Push source strings and pull completed translations through the Transifex API 3.0 (JSON:API) for a continuous localization pipeline
domain: developers.transifex.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Authenticate with a Bearer API token and set the Content-Type/Accept headers to application/vnd.api+json as required by the JSON:API spec
Create or update a resource's source strings by POSTing to resource_strings_async_uploads (or the strings endpoint) with the source content, base64-encoding non-JSON-serializable formats (e.g., .docx, .xlsx, .idml)
Poll the async upload resource until its status is completed to confirm strings were parsed and created
Fetch completed translations via GET resource_translations, filtered by resource and language, then trigger an async translations download if pulling a full file
Filter by review/translation status fields on the translation resource to only pull strings that have passed the desired workflow stage
Known gotchas
Requests must use the application/vnd.api+json content type and JSON:API resource/relationship shape — plain JSON bodies in the old REST style are rejected
Uploads and downloads are asynchronous jobs (resource_strings_async_uploads / resource_translations_async_downloads); the initial POST only returns a job reference to poll
As of recent API versions, Transifex's REST API has no dedicated glossary endpoints — glossary/termbase management is a dashboard/CSV-import feature, not something this API can drive
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?