Export data
GET/v2/projects/:projectId/export
Export data
Request
Path Parameters
Query Parameters
Languages to be contained in export.
If null, all languages are exported
Possible values: [JSON
, JSON_TOLGEE
, XLIFF
, PO
, APPLE_STRINGS_STRINGSDICT
, APPLE_XLIFF
, ANDROID_XML
, FLUTTER_ARB
, PROPERTIES
, YAML_RUBY
, YAML
]
Format to export to
Delimiter to structure file content.
e.g. For key "home.header.title" would result in {"home": {"header": "title": {"Hello"}}} structure.
When null, resulting file won't be structured. Works only for generic structured formats (e.g. JSON, YAML),
specific formats like YAML_RUBY
don't honor this parameter.
Filter key IDs to be contained in export
Filter key IDs not to be contained in export
Filter keys tagged by
Filter keys with prefix
Possible values: [UNTRANSLATED
, TRANSLATED
, REVIEWED
, DISABLED
]
Filter translations with state. By default, all states except untranslated is exported.
Filter translations with namespace. By default, all namespaces everything are exported. To export default namespace, use empty string.
If false, it doesn't return zip of files, but it returns single file.
This is possible only when single language is exported. Otherwise it returns "400 - Bad Request" response.
Possible values: [C_SPRINTF
, PHP_SPRINTF
, JAVA_STRING_FORMAT
, APPLE_SPRINTF
, RUBY_SPRINTF
, ICU
]
Message format to be used for export.
e.g. PHP_PO: Hello %s, ICU: Hello {name}.
This property is honored only for generic formats like JSON or YAML.
For specific formats like YAML_RUBY
it's ignored.
If true, for structured formats (like JSON) arrays are supported.
e.g. Key hello[0] will be exported as {"hello": ["..."]}
Responses
- 200
- 400
- 401
- 403
- 404
OK
- application/json
- Schema
- Example (from schema)
Schema
object
{}
Bad Request
- */*
- Schema
Schema
string
Unauthorized
- */*
- Schema
Schema
string
Forbidden
- */*
- Schema
Schema
string
Not Found
- */*
- Schema
Schema
string