Skip to main content

Platform management errors

Platform route errors use {error:{code,message,requestId}}; ingress refusals can omit requestId. Preserve a supplied request ID for support, but never expose secrets or capability URLs in logs. Error codes are not interchangeable with the Queue API’s uppercase codes. HTTP 202 is an accepted background operation, not completed Ready/publication/upload work. Poll its own receipt until success or terminal failure. Server success does not prove physical Player activation.

Queue API errors

Queue API errors use:
Never parse the human-readable message. Log the stable code, HTTP status, correlation ID, and operation identity. Do not log API keys, raw PINs, or webhook secrets.

Structured Widget Push errors

Structured Widget Push uses the same { "error": { "code", "message" } } shape and can include details for schema issues. Schema errors can include an issue list under error.details. Correct those fields before retrying.