Create a publishable key
/api/v1/publishable-keysMints a new publishable key of the given type. A web key delivers refresh tokens as an httpOnly cookie the browser guards; a native key returns them in the response body for a phone app to store in the OS keychain. The type is fixed at creation — a key cannot be converted later, because sessions already issued from it carry the delivery it implied. An Environment holds at most 10 live keys; one more returns 409 (publishable_key.limit).
Authentication
Authorization Option A JWT access token. Never send alongside X-API-Key: a request carrying both is refused.
X-API-Key Option B API key for management-tier access. Never send alongside an Authorization header: a request carrying both is refused.
publishable_key.manageAuthenticationCreate, rename, and revoke the Environment's publishable keys. Held only when named: full access does not include it. A scoped API key must hold it as a scope; a full-access key holds every scope within its Environment except the named-only and account scopes; a developer's token needs the Console capability that covers it. A credential without it is refused with 403.
Headers
X-Canopy-EnvironmentThe id of the Environment this request acts in. Required with an account API key, which belongs to the Account and names its Environment per request; an Environment key may send it only to name its own Environment. A missing header for an account key answers `400` (`api_key.environment_required`), one naming no Environment of the key's Account `400` (`api_key.environment_not_found`), and one naming another Environment than an Environment key's own `400` (`api_key.environment_mismatch`).
Request body
application/json
typeenum Required What kind of app will hold this key, which decides how a session created with it receives its refresh token. `web` delivers an httpOnly cookie the browser guards; `native` returns the token in the response body for a phone app to store in the OS keychain. Fixed at creation — a key cannot be converted later, because sessions already issued from it carry the delivery it implied.
namestring Required Label shown in the dashboard, so several keys on one environment are tellable apart (e.g. "iOS app", "marketing site").
Responses
application/json
data *PublishableKeyResponseDto
application/json
error *ApiErrorBodyDto
application/json
error *ApiErrorBodyDto
application/json
error *ApiErrorBodyDto
application/json
error *ApiErrorBodyDto
Errors
When the request can't be completed, the response body includes a stable error code you can branch on, and a correlation_id (also sent as the X-Correlation-Id header). Quote the correlation id when you contact support: it identifies the exact request in Canopy's logs. A request refused by an authorization check answers 403 with the code authorization.denied, and its data names the denial_reason and the permission checked.
authorization.deniedForbiddenThe credential does not hold the permission this operation checks: a scoped API key without the scope, a developer without the Console capability that covers it, or a permission granted somewhere other than the node the request targets. The error's data names the permission.
Add the permission named in the Authentication section to the key's scopes, or ask an account administrator to grant the covering capability, then retry. For a node-scoped operation, make sure the grant reaches the node you are acting on.
Returned object
curl -X POST "https://auth.canopy-io.com/api/v1/publishable-keys" \ -H "X-Canopy-Environment: value" \ -H "X-API-Key: $CANOPY_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "type": "web", "name": "string" }'
{ "data": { "id": "string", "key": "string", "type": "web", "name": "string", "created_at": "2026-04-20T12:00:00.000Z" } }
Tell us how we can improve this guide.