Changelog and the versioning promise

The versioning promise

Everything under /v1 changes additively only: new routes, new optional request fields and new response fields may appear, and nothing you rely on is renamed, removed or made to mean something else. Read responses so that a field you do not know is ignored. A change that could break an integration would be a new version, /v2, announced here with the date /v1 stops.

15 September 2026

• turn on POST /v1/documents/{document_id}/pages/{page_index}/ocr and POST /v1/documents/{document_id}/pages/{page_index}/preflight: 0, 90, 180 or 270, clockwise. The page is read turned that way, as a viewer shows a page that was saved sideways, and every box, in the request and in the answer, stays in the page's own pixels. Optional: without it, or at 0, a page is read as its file has it, as before.

v1 — 12 September 2026

The first published version of the API.

• API keys for Business accounts, with a lifetime of 7, 30 or 90 days, or none.
• Keys stop immediately when revoked, and permanently when the Business plan ends.
• One list of the routes a key may call; everything else refuses a key with 403 not_available_to_api_keys.
• A rate limit per key, with X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset on every response.
• Verification certificates, and the public routes that check them.