Skip to main content
POST
/
integration
/
content
/
import
curl -X POST "https://api-integration.ollang.com/integration/content/import" \
  -H "X-Api-Key: <your-api-key>" \
  -H "Content-Type: application/json" \
  -d '{
    "targetLanguage": "de",
    "translations": [
      { "sourceText": "Good morning", "targetText": "Guten Morgen" },
      { "sourceText": "Sign in", "targetText": "Anmelden" },
      { "sourceText": "Dashboard", "targetText": "Übersicht" }
    ]
  }'

{
  "success": true,
  "imported": 3
}

Documentation Index

Fetch the complete documentation index at: https://api-docs.ollang.com/llms.txt

Use this file to discover all available pages before exploring further.

Import translation units (source text + target text pairs) into your content database. This is useful for bulk-loading translations from external systems, TMS exports, or programmatic workflows. Imported content terms become immediately available in the Content Management page and can be exported, tagged, and edited. 
curl -X POST "https://api-integration.ollang.com/integration/content/import" \
  -H "X-Api-Key: <your-api-key>" \
  -H "Content-Type: application/json" \
  -d '{
    "targetLanguage": "de",
    "translations": [
      { "sourceText": "Good morning", "targetText": "Guten Morgen" },
      { "sourceText": "Sign in", "targetText": "Anmelden" },
      { "sourceText": "Dashboard", "targetText": "Übersicht" }
    ]
  }'

​
Authorizations

This endpoint requires API key authentication. Include your API key in the request header:
  • Header name: X-Api-Key
  • Header value: Your API key from the Ollang dashboard

​
Body Parameters

​
targetLanguage
string
required
The target language code for all translations in this import batch (e.g., de, fr, ja). All translation units in the translations array must be in this language.
​
translations
array
required
Array of translation units to import. Each unit represents a source-target text pair.

​
Behavior

  • If a content term with the same sourceText already exists, a new target entry for the specified language is added (or the existing one is updated).
  • If the sourceText does not exist, a new content term is created with the provided translation.
  • Import is idempotent for the same sourceText + targetLanguage combination — re-importing updates the target text.

​
Response

​
success
boolean
Whether the import completed successfully.
​
imported
number
The number of translation units that were processed.
{
  "success": true,
  "imported": 3
}