1. Keep source language authoritative
Store the source strings in your product repository and send them to LangKit with a project-scoped token. Avoid using a global administrator credential inside CI.
2. Preview changes before applying
Request an import preview and inspect changed/new values. Save the preview checksum with the apply request. Rejecting a stale preview is safer than overwriting a concurrent translator edit.
3. Translate selectively
Queue a background job for missing or outdated target entries. Track status until it finishes, then send human reviewers only the strings requiring attention.
4. Export and test
Export the desired target files after approvals. Run your application build and formatting tests, including placeholder and plural validation. Only an integrated app can actually receive the updated strings.
Common questions
Do I need to poll all strings?
A cursor-based change feed helps clients fetch only changes.
Can a job continue after CI exits?
Jobs are persisted separately and can be checked using the status API.
Before relying on this in production
Confirm support for your resource syntax and test exported translations in your application. Documentation describes supported workflows, not a guarantee of lossless conversion for every specialized format.