SMsmartling
translations

Import translations from offline CAT tool (XLIFF)

Changed on

Imports a translated XLIFF file from an external CAT tool. Translations are tagged with OFFLINE_CAT origin.

Import may partially succeed — some strings may fail validation while others are imported successfully. Check translationImportErrors in the response for per-string errors.

Use workflowStepUid to target a specific workflow step. When submitContent=true, content is automatically advanced to the next workflow step after import.

When mtContent=true, imported translations are tagged with OFFLINE_CAT_MT origin instead of OFFLINE_CAT, and are saved with EXTERNAL translation quality instead of the default human quality. Use this to isolate machine-translated test content from TM matching against human translations.

Limitations

  • Limit calls to 6 requests per 60 seconds per user. Exceeding this returns 429.
post/translations-api/v2/projects/{projectId}/locales/{localeId}/content

Request

  • Base URL
    https://api.smartling.com
  • Auth
    HTTP bearer

Path parameters

projectIdstring required

Unique identifier of a Smartling project — 9 lowercase alphanumeric characters.

Example:84c012a33

A unique project identifier. This can be found in the Smartling Dashboard under Account Settings > API.

localeIdstring required

Locale identifier. Either a 2-letter language code (en) or a language-region pair (en-US). The language part is always lowercase; the region part is always uppercase.

Example:fr-FR

Query parameters

workflowStepUidstring

Workflow step unique identifier — 12 lowercase alphanumeric characters.

Example:7564fc097a85

Import translations into this specific workflow step.

submitContentboolean

Automatically advance content to the next workflow step after import.

mtContentboolean

Tag the imported translations as machine-translated (OFFLINE_CAT_MT origin, EXTERNAL quality) instead of the default human-translated (OFFLINE_CAT origin) tagging.

Request body multipart/form-data

filestring binary required

Translated XLIFF 1.2 file.

Response

Import completed. Check translationImportErrors for per-string failures.

Example response

{
  "response": {
    "data": {
      "translationImportErrors": [
        {
          "stringHashcode": "d41d8cd98f00b204e9800998ecf8427e",
          "fileUri": "/content/en/home.json"
        }
      ]
    }
  }
}

Changes