Upload translated XLIFF asynchronously
Upload translated XLIFF back to Optimizely. The connector parses the XLIFF, maps target-language segments back onto the original content items, and writes them to the target locale in the configured project.
Async variant. Returns immediately with { requestId, webHookUrl }. The upload result is POSTed to the URL supplied in X-Webhook. X-Webhook is required.
Authorizations
IDM-issued JWT. Obtain via the IDM authentication flow and pass as: Bearer
Headers
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.
Required on /async/... endpoints. Bifrost POSTs the operation result to this URL once the connector finishes processing.
Omitting this header on an async endpoint returns 400.
Body
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.
UUID of a connector instance configured in TMS.
"4282fec0-d2e9-4266-8733-3e634feb7b59"
Optimizely-specific behavior knobs.
Selector inside the Optimizely project — content item, folder, or ROOT.
Source locale embedded in the XLIFF (Optimizely locale code).
"en"
Target locale to write into (Optimizely locale code).
"de"
Storage ID of the translated XLIFF file (already uploaded to Phrase file storage).
"e48eda63928c4155bez9fdbsaadc15f3"
Response
Successful operation. If X-ResponseType is set to 'ID' or no value is sent in the header, the file is saved and can be retrieved by sending a GET request to this endpoint. If X-ResponseType is set to 'OBJECT', the file is returned as a stream.