Get a client token
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-tokens/{clientTokenId}Authorization
Path parameters
Returns
200
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.
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.