Convert stored XLIFF back to raw Optimizely content asynchronously
Convert a translated XLIFF (referenced by storageId) back into Optimizely’s raw
content format without writing it to Optimizely. The result is stored in Phrase file
storage and returned as a storageId you can then push with upload-raw-file.
Use this when the upload step is decoupled from the conversion step (e.g. for a preview/review gate).
Async variant. Returns { requestId, webHookUrl } immediately; the raw file (or its storageId) is POSTed to X-Webhook.
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.
Specify if the response should contain the processed object itself in an application/octet-stream body, or a application/json body with an ID that can be then used to retrieve the object using a /load-content endpoint. Note that for larger files (> 1 MB), it is advised to use the ID option which is also default.
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 converting a stored XLIFF back into Optimizely's raw content format without writing it to Optimizely. The result lands in Phrase file storage as a new storageId you can then push with upload-raw-file.
Storage ID of the translated XLIFF file to convert.
"e48eda63928c4155bez9fdbsaadc15f3"
Source locale embedded in the XLIFF (Optimizely locale code).
"en"
Target locale the XLIFF was translated into.
"de"
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.