Skip to content
ANKK APPANKK Docs

Error Handling

Read the HTTP status and response body together. Error fields vary by endpoint; use the API reference for the exact contract.

  • For a timeout or temporary 5xx failure, first inspect any returned content or job identifier. If retrying the same operation, keep the same payload and idempotency_key and use bounded backoff. HTTP 202 means acceptance, not successful publication.
  • For 409 idempotency_conflict, compare the original request and its result. Do not automatically generate a new key. Use a new key only for an intentionally new operation after reconciling the previous one.
  • Correct invalid input or authentication/permission failures before retrying. For 429, inspect the error and Retry-After when present: exhausted plan quotas may require a reset or plan change, not a short delay.
{
  "error": "insufficient_scope",
  "message": "publishing:write scope is required for this API request."
}