Changelog: October 2026

Changes to the API and to this documentation published in October 2026, newest first.

2026-10-13 – 1.73.0, the API's bare address opens the documentation

https://api.doc.cheap/ now answers 301 Moved Permanently to https://doc.cheap/docs, so a person who types the API's address into a browser lands on the documentation instead of a not_found error. Only the bare origin moved: /v1/..., /healthz and every other path answer exactly as before.

2026-10-11 – 1.72.0, country codes as the document writes them

A passport's machine-readable zone writes country codes by ICAO Doc 9303, which is almost, but not quite, ISO 3166-1 alpha-3. Germany writes D, British passports carry five nationality codes of their own such as GBD, and stateless persons, refugees, the United Nations and a few organisations have codes ISO does not have.

document.issuing_state_detail and holder.nationality_detail are new. Each gives the code as written, its ISO 3166-1 alpha3 and alpha2 (null when ISO has none) and a category such as iso, icao_variant, british_nationality, stateless or refugee. Country codes has the full list.

A fix comes with it: a German document used to give null in document.issuing_state and holder.nationality, because D is not three letters. Both now say DEU. Every other code is returned exactly as before, ICAO-only codes such as GBD and XXA included, so code that reads those fields keeps working.

2026-10-09 – 1.69.1, the public sandbox key keeps its scans for a year

The documentation now says what the public sandbox key, sk_sandbox_public, does with a scan. Every scan made on it is kept for one year, with no account, the address it came from, the reading and a micro thumbnail, and retain_hours is not applied on that key. The key cannot read, list or delete those scans, and the retention sweep deletes them when the year is up. An earlier page said they were never stored, which was wrong. Data retention and privacy has the details. An account's own sandbox key still stores nothing.

2026-10-04 – 1.63.0, client tokens: scan from an app without the key

POST /v1/client-tokens issues a short-lived token with an API key. A browser or a mobile app sends POST /v1/scans with that token, so the key stays on your server. A token lives 300 seconds and allows one scan request by default, up to 900 seconds and 10 requests. It can call nothing but POST /v1/scans, its scans are billed and stored exactly as the issuing key's, a sandbox key issues sandbox tokens, and revoking or deleting the key ends its tokens.

Three error codes come with it: 401 client_token_expired, 401 client_token_used_up and 403 client_token_not_allowed. Read a passport in an Ionic app gains a second option built on it.

A POST sent with no body at all is now refused with 400 invalid_request instead of 500 internal_error.