Export translations as per-language files
Render the project’s translations to files in the chosen format — one file per language, with each file’s contents base64-encoded in contentBase64. Use ?languages= to export a subset and ?status=approved to ship only approved strings; ?branch= exports a branch’s overlay. See the import/export guide and the supported file formats.
Constraints:
- One file is emitted per target language, so the response shape is uniform across single- and multi-language formats.
Authorizations
API token: tsu_pat_… (PAT) or tsu_proj_… (project token). The token's granted RBAC permissions determine access; see each operation's x-permission.
Path Parameters
Project id (UUID) or id-embedded path slug.
Query Parameters
Target format id, e.g. json-nested. See GET /projects/{projectId}/formats.
1Comma-separated language codes, e.g. fr,de. Omitted = all project languages.
Only include values in this approval status (e.g. approved).
all, approved, pending_review, draft Target an open translation branch instead of main. Required when the project's main branch is protected.

