Skip to main content
POST
Upload translated XLIFF synchronously

Authorizations

Authorization
string
header
required

IDM-issued JWT. Obtain via the IDM authentication flow and pass as: Bearer

Headers

X-ActionId
string

A logging ID of the request. It is propagated through Phrase systems, making it easier to connect logs from various services. If no ActionId is sent with a request, one will be generated by Bifrost and returned with the response.

Body

application/json

Request body for uploading translated XLIFF back to Optimizely. Reference the stored XLIFF by storageId; the connector parses it and writes the target-locale segments to Optimizely.

connectorUuid
string
required

UUID of a connector instance configured in TMS.

Example:

"4282fec0-d2e9-4266-8733-3e634feb7b59"

configuration
object
required

Optimizely-specific behavior knobs.

path
object
required

Selector inside the Optimizely project — content item, folder, or ROOT.

sourceLocale
string
required

Source locale embedded in the XLIFF (Optimizely locale code).

Example:

"en"

targetLocale
string
required

Target locale to write into (Optimizely locale code).

Example:

"de"

storageId
string
required

Storage ID of the translated XLIFF file (already uploaded to Phrase file storage).

Example:

"e48eda63928c4155bez9fdbsaadc15f3"

Response

Success — the XLIFF was parsed and written. The envelope reports success and any per-item errors returned by Optimizely.