Convert stored raw Optimizely content to XLIFF asynchronously
Convert raw Optimizely content already in Phrase file storage to XLIFF 2.0, without
re-downloading from Optimizely. Each entry in rawFiles references a stored file
(storageId) plus the metadata the connector needs to segment correctly.
Use this when you have a snapshot from download-raw-file and want to defer the
conversion step (e.g. to apply custom pre-processing first).
Async variant. Returns { requestId, webHookUrl } immediately; the XLIFF (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 already-stored raw Optimizely content into XLIFF 2.0 without re-downloading from Optimizely.
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.