POST /v1/i18n/repo-translations

Authentication

Send an API key as a bearer token. The endpoint checks translations.register; a key without it is refused with 403, not 404.

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 POST https://api.zinndigital.com/v1/i18n/repo-translations \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "items": <object[]> }'

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

i18n fix A (2026-10-16): when a lane commits a translation into the repository after the engine translated the SAME English, the repository's copy wins, and the export (scripts/i18n-sync.mjs export) hands it back here so the engine and the repo hold one truth. Each item is accepted only while source_hash still equals the string's current English hash; an item whose English moved on (stale) or whose string is unknown (missing) is reported and left alone, so a changed source keeps re-translating through the ordinary batched pipeline (CLAUDE.md §2.19). An accepted row is up_to_date, its translated_at is now, and it is attributed repo — indistinguishable from any other translation to every consumer. Idempotent: the same text again changes nothing.

Parameters

Request body

Response

Errors this endpoint can return

401 · 403 · 422 · 429