Errors and troubleshooting
Public-layer errors include a machine-readable code and requestId, also exposed in the X-Request-Id header:
{"error":{"code":"INSUFFICIENT_SCOPE","message":"This credential does not permit this operation.","requestId":"HTTP_REQUEST_ID"}}| HTTP / code | Next step |
|---|---|
401 INVALID_CREDENTIAL |
Check key/token validity and revocation; reconnect OAuth if necessary |
403 AUTOMATION_REQUIRED |
Check base access and API + MCP in Subscription/Integrations |
403 INSUFFICIENT_SCOPE |
Use the exact required permission rather than unnecessarily broad access |
404 NOT_FOUND |
Check ID and account; other accounts’ resources are not revealed |
409 IDEMPOTENCY_CONFLICT |
This key identifies another payload; retrieve the original intent |
409 on cancellation/deletion |
Work has started or a reference is in use; do not force the operation |
410 |
Visible content/request expired; this does not authorize automatic regeneration |
413 BODY_TOO_LARGE / REFERENCE_TOO_LARGE |
Reduce the body/image to supported size |
415 INVALID_CONTENT_TYPE |
Use JSON for JSON routes |
422 INVALID_PARAMETER / BATCH_LIMIT |
Correct the payload or retrieve plan capabilities |
429 DAILY_VIDEO_LIMIT |
Wait for returned resetsAt; additional keys do not bypass it |
429 REQUEST_RATE_LIMIT |
Follow Retry-After and reduce polling |
429 for queue/pacing |
Wait for capacity; preserve the identity of an already sent request |
503 |
Maintenance or temporary unavailability; retain IDs and retry safely |
An assistant cannot connect
Section titled “An assistant cannot connect”Check /mcp, Streamable HTTP support, OAuth/PKCE and automation access. Start a new connection if consent expired. Revoking and reconnecting an old connection does not require repeating earlier generations.
If a client sends Origin, it must be allowed. Never work around an Origin error by weakening browser security.
Payment confirmed but automation inactive
Section titled “Payment confirmed but automation inactive”Open Subscription and refresh status. Returning from checkout is not payment evidence; activation depends on a verified notification. Do not buy automation twice while the first purchase is pending confirmation.
When contacting support, include requestId, generation ID and approximate time. Never send an API key, token, cookie, card data or private download URL.