Crowdin

Crowdin is widely used across both open-source and commercial software projects, with particular strength in community-driven translation workflows where volunteers contribute translations alongside professional translation services. The API enables automation of the localization pipeline — syncing source files, monitoring translation progress, downloading translated files — making continuous localization feasible alongside development workflows.

The API v2 is comprehensive: file management, translation progress, glossary, TM (translation memory), and integration webhooks. The file-centric design reflects Crowdin's heritage as a platform that manages locale files (JSON, YAML, PO files, etc.) rather than individual string keys, which suits certain development workflows better than key-based platforms. Agents can push updated source files and retrieve translations in the same format.

Authentication uses API tokens with project-level or organization-level scope. The token-based model is appropriate for automation workflows. Teams with multiple projects should use project-scoped tokens for pipeline automation rather than organization-level tokens that have broader access.

Reliability is production-grade and the API is battle-tested across a large number of integration deployments given Crowdin's market presence. Translation job processing is asynchronous; webhook delivery for completion events is the appropriate integration pattern for agents that need to act on completed translations without polling.

Documentation is thorough and covers both the API reference and integration patterns. The guides for CI/CD integration are particularly useful — Crowdin has invested in developer experience around the automation use cases that agents need. Teams new to localization automation will find the conceptual guides helpful alongside the endpoint reference.