Activate browser key

POST/v1/browser/activate

Use this from browser integrations before creating jobs. Send the publishable key in the JSON body; the API validates the Origin header against the key's allowed-origins list.

AUTH

No Authorization header; publishable key in JSON body with allowed Origin

CONTENT TYPE

application/json

STATUS

Stable
Publishable key in request bodySandbox thisOpen as Markdown ↗

Request parameters

publishable_key
string
Required
Publishable key shown once in the dashboard.
Origin header
string
Required
Browser origin that must match an allowed origin for the publishable key.

Returns

ok
boolean
True when activation succeeds.
activation_token
string
Short-lived token bound to the project and origin.
expires_at_ms
integer
Unix epoch milliseconds for token expiry.
key_id
string
Activated publishable key identifier.
wrapper_tenant_id
string
Wrapper tenant bound to the token.
project_id
string
Project bound to the token.

Errors

unauthorized401

Missing or unknown publishable key.

forbidden403

Origin is not allowed for this key.

validation_error400

publishable_key is missing or malformed, or the Origin header is absent.

Related

Need rollout review?

Start with the Server API. Use contact only when you need rollout review, enterprise coordination, or non-standard integration help.

Contact the team