Read an error
Errors use a JSON envelope: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 documentIdempotency-Key can protect retries against duplicate writes. Generate one unique key per logical action and keep it stable across retries of that same action.
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 asidempotencyKey; 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.