Public Vendor Catalog
Read-only access to the supported vendor and model catalog. Use it to render a vendor/device picker or browse onboarding options. No userId is required.
TL;DR
GET /v1/catalog/vendors→GET /v1/catalog/vendors/{vendorId}→GET /v1/catalog/vendors/{vendorId}/connection-options- Authentication is optional. Send your
Authorization: Bearertoken to get the catalog scoped to your white-label app; call anonymously to get the default clever-PV catalog. NouserIdis needed either way. - Connection-option placeholders are returned as readable documentation tokens (e.g.
HOME_OCPP_ID) because there is no home/user to resolve them against. To actually onboard a device, switch to the authenticated Device Onboarding Flow.
Authentication (optional)
| Call style | Catalog returned |
|---|---|
| Anonymous (no token) | The default clever-PV catalog. |
Authenticated (Authorization: Bearer <token>, same token as the rest of the Connect API) | The catalog scoped to your partner's white-label app — i.e. exactly the vendors/models your app users can onboard. |
Scoping applies to List Vendors and Get Vendor. If the token is missing or its app cannot be resolved, the response falls back to the default clever-PV catalog. Get Connection Options always returns documentation tokens regardless of authentication (see below).
List Vendors
Code
Returns the clever-PV catalog when called anonymously, or your app-scoped catalog when authenticated.
category (query, optional) filters by device category. Values (camelCase): electricMeter | wallbox | switch | powerStorage | car | heatPump | heatingRod | dishwasher.
Response: paginated list of vendors.
Code
| Field | Notes |
|---|---|
identifier | Stable machine-readable vendor key. |
flow | Onboarding flow: form | oidcProxy | oidc | ocpp | push. See Device Onboarding Flow. |
models[] | Supported device models, each with id, name and category. |
Get Vendor
Code
Returns a single vendor in the same shape as a data[] entry above, scoped the same way (anonymous → clever-PV catalog, authenticated → your app-scoped catalog). 404 Not Found if the vendor is not in the resolved catalog.
Get Connection Options
Code
Same response shape as the authenticated Step 2: Get Connection Options, but placeholders are replaced with documentation tokens instead of resolved per-home values. This endpoint is not app-scoped and returns the same documentation tokens whether or not you authenticate — there is no home/user on this route to resolve real values against.
Code
Note: Tokens like
HOME_OCPP_IDorDEVICE_TAGare placeholders for documentation only. Real, resolved values are minted by the authenticated onboarding flow (POST /connections).404 Not Foundif the vendor is not in the catalog.