Export Formats

LinguLink supports five export formats:

JSON for application runtime consumption
CSV for spreadsheet-first workflows
XLIFF for translation tooling and localization vendors
XML for legacy or platform-specific pipelines
YAML for config-driven i18n setups

Pass the format via the format query parameter on the export endpoint (json, csv, xliff, xml, yaml). json is the default. Responses use the matching content type — application/json, text/csv, application/xml (XLIFF and XML), or text/yaml — so scripts can pipe the body straight to a file with the right extension.

Choosing a Format

Use JSON for i18n runtime libraries and deploy pipelines
Use CSV when translators or PMs iterate in spreadsheets
Use XLIFF when handing off to a translation agency or CAT tool
Use XML / YAML to match an existing runtime’s expected file shape

Export Quality Checks

Validate locale coverage
Validate placeholder consistency
Confirm environment-specific overrides

Example JSON Output

{
  "auth": {
    "login": {
      "title": "Sign in",
      "submit_button": "Continue"
    }
  }
}

Pick the format based on your downstream system and automation needs.

Next Steps

Bring data in via Import Translations
Wire automation from Integration Examples

Integration Examples Environment Overrides

Overview

Getting Started

Project Management

Translation Management

API and Integrations

Help and Support

Choosing a Format

Export Quality Checks

Example JSON Output

Next Steps

​Choosing a Format

​Export Quality Checks

​Example JSON Output

​Next Steps

Choosing a Format

Export Quality Checks

Example JSON Output

Next Steps