Create a client token
A client token is publishable by design: it goes in web pages and is sent by browsers to obs-browser.ezghcloud.com as ?ct=. It can only send RUM data for its application into its dataset, from its allowed origins, within its limits. Send datasetId (an existing dataset of the project) or environment (its dataset, created when the project has none, which also needs obs.datasets.create). limits fields left out are the defaults (500 requests/s, 50 MiB/s, 20 GiB/day, 6,000 errors/minute); each may be at most the project's ceiling (10x the defaults unless raised). 400 invalid_request with issues[] for every validation problem, each at its field's dotted path. 409 quota_exceeded: obs.clientTokens.perProject. 409 dataset_deleting. 409 organization_deletion_pending. 404 while real user monitoring isn't offered (GET client-tokens is the console's probe).
https://obs.ezghcloud.com/v1/organizations/{orgId}/projects/{projectId}/obs/client-tokensAuthorization
Path parameters
Header parameters
Request bodyJSONrequired
Returns
201
The client token.
- allowedOriginsarray ofstringrequired
1-50 origins browsers may send from: https://shop.example.com, https://.example.com (one or more whole labels) or http://localhost:.
400
invalid_request (with issues), invalid_cursor, or the endpoint's own 400 codes.
403
access_denied: the caller's policies don't allow the action; forbidden_origin: a cookie-authenticated write from an origin that isn't allowed; spend_limit_reached.
404
not_found: unknown, malformed, or in an organization the caller isn't in.
409
quota_exceeded (an allocation quota, with quota), idempotency_conflict, idempotency_in_progress (with Retry-After), organization_deletion_pending, operation_in_progress, or the endpoint's own 409 codes.
413
payload_too_large: the body is over the endpoint's limit (1 MiB unless it says otherwise).
429
too_many_requests, with Retry-After; or quota_exceeded (a rate, usage or concurrency quota, with quota), never with Retry-After.
500
internal_error: a bug; the details are in the logs, under the request ID.