GET /v1/i18n/documents/{locale}

Authentication

This endpoint is public. It takes no credential and no organisation — it is what our own marketing site and AI answer engines read.

This endpoint takes no organisation id. Your key already identifies the organisation it belongs to, and the response is scoped to it.

Try it

Replace anything in angle brackets with your own values, and the key placeholder with a key from your dashboard.

curl -X GET https://api.zinndigital.com/v1/i18n/documents/{locale}?object_ref=<object_ref>

Signed in? The API console in your dashboard fills in your real organisation id and your own key, and runs the request against the live API so you can see the actual response. Open this endpoint in the API console

Details

Returns the finished translations for a single document, as field -> text across the surfaces a rendered page is built from (page, meta_title, meta_description, alt_text) — the read the public site performs on the server, per page, at render time. Why a second public endpoint next to getPublicMessageCatalogue. They are cached on different keys and answer different questions. The catalogue is one response per locale covering the shell (nav, footer, meta) and is read on every page; this is one response per document per locale, read only by the page it belongs to. Folding them together would churn the shell's cache entry whenever any of 60 marketing pages was retranslated. ⛔ object_ref is required. One locale's whole page surface is ~7,879 entries — the read scripts/i18n-pages.mjs batches at build time, and the one that OOM-killed the engine on 2026-08-05. Making the parameter optional would re-create that on a public, unauthenticated URL. A single document is ~131 leaves, which is what makes this safe on a render path behind an edge cache. Public and non-tenant, for the same reasons as the catalogue: the text is already in the page's HTML, and an Authorization header suppresses shared caching. up_to_date only — the site applies this over the document the current deploy already serves, so stale text could only replace a good translation with an older one. An untranslated document is a 200 with an empty fields object, never a 404 — the caller treats any failure as "use the build-time document", so a 404 would be indistinguishable from an outage. Cacheable: strong ETag plus Cache-Control: public, max-age=300, stale-while-revalidate=86400.

Parameters

Response

Errors this endpoint can return

422 · 429