POST/v1/browser/activate

Activate browser key

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.

Publishable key flowNo Authorization header; publishable key in JSON body with allowed OriginSandbox this

Request parameters

NameTypeRequiredDescription
publishable_keystringRequiredPublishable key shown once in the dashboard.
Origin headerstringRequiredBrowser origin that must match an allowed origin for the publishable key.

Returns

NameTypeDescription
okbooleanTrue when activation succeeds.
activation_tokenstringShort-lived token bound to the project and origin.
expires_at_msintegerUnix epoch milliseconds for token expiry.
key_idstringActivated publishable key identifier.
wrapper_tenant_idstringWrapper tenant bound to the token.
project_idstringProject bound to the token.

Request example

POST /v1/browser/activate

activate.shbash
1curl -X POST https://api.wavebird.ai/v1/browser/activate \2  -H "Origin: https://publisher.example" \3  -H "Content-Type: application/json" \4  -d '{5    "publishable_key": "pk_test_wavebird_demo_publishable"6  }'

Response example

Response

response.jsonjson
1{2  "ok": true,3  "activation_token": "wbat_demo_eyJhbGciOi...",4  "expires_at_ms": 1777032600000,5  "key_id": "key_demo_123",6  "wrapper_tenant_id": "wbt_demo_123",7  "project_id": "wbproj_demo_8jK42"8}

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.