Skip to main content
Doconda returns errors as application/problem+json (RFC 9457) with a stable code. Decide what to do from code and the HTTP status, never from the text.
In the SDKs, a failed request raises DocondaError with status, code, request_id and errors.

Request and authentication

Billing and limits

Files

Documents

| idempotency_key_reused (422) | This Idempotency-Key was already used with a different body. | Send a new key for a different document; see idempotency. | | idempotency_request_in_progress (409) | The first request with this key is still being accepted. | Retry in a few seconds with the same key. |

Saving a hand-edited file

These come from PUT /documents/{id}/file (see save a hand-edited file). If the save is accepted but the file can’t be processed, the request answers 422 with that failure’s code, and the document stays as it was.

Artifacts

See artifacts for all the limits.

Webhooks and editor

Server

The SDKs retry network errors, 429 and 5xx responses up to 2 times by default (max_retries in Python, maxRetries in TypeScript), only for reads and for requests with an Idempotency-Key.

Language of messages

title, errors[].message and a failed document’s error.message follow the request’s Accept-Language header: Spanish for es, English for anything else, and English when the header is missing. A document’s error.message is written in the language of the request that created it. In the SDKs, set language="es" (Python) or language: "es" (TypeScript) when you create the client. Codes never change with the language.

When a document fails

A problem found while the document is being made can’t be an HTTP error: the request was already accepted. The document ends with status: "failed", document.failed arrives, and error.code says why. Failed documents are not charged.

Idempotency

Idempotency lets you retry POST /documents without creating, or paying for, the same document twice. Send an Idempotency-Key header with a unique value per document:
  • The same key and the same body within 24 h, in the same project, return the same document.
  • The same key with a different body is rejected with 422 idempotency_key_reused.
  • A retry that arrives while the first request is still being accepted gets 409 idempotency_request_in_progress: retry in a few seconds.
Only POST /documents uses the header. The SDKs send a new key on every create() call and reuse it on their own retries; pass your own to make your retries safe too.

Get help

Write to us from the contact form on the website, with the request_id of the failed request or the doc_… ID of the failed document.