Skip to main content

Read an error

Errors use a JSON envelope:
Some errors include details. Log the HTTP status, error code, and X-Request-Id response header. Exclude API keys and customer message bodies from logs unless your own data policy requires them.

Use idempotency for supported writes

Endpoints that document Idempotency-Key can protect retries against duplicate writes. Generate one unique key per logical action and keep it stable across retries of that same action.
Retry with the same method, endpoint, query, body, and key. Do not reuse the key for a different action. A replay may include Idempotency-Replayed: true. Conflicting payloads or an in-progress request can return 409. If a write times out, it may already have completed. Use the original idempotency key when the endpoint supports it; otherwise inspect the resource before repeating the operation.

Retry Help Center proposals

Authoring writes require an idempotency key. MCP proposal tools take it as idempotencyKey; HTTP requests use the header. Use 8–128 printable, non-space ASCII characters. For a revision conflict, fetch the latest article and ask for a new review decision. Do not silently overwrite newer content. An uncertain network result should be retried only with identical arguments and the original key.