Skip to main content
POST
Convert stored XLIFF back to raw Braze content asynchronously

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.

X-ResponseType
string

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.

X-Webhook
string
required

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

application/json

Request body for converting a stored XLIFF back into Braze's raw multilingual content format without writing it to Braze. The result lands in Phrase file storage as a new storageId you can then push with upload-raw-file.

storageId
string
required

Storage ID of the translated XLIFF file to convert.

Example:

"e48eda63928c4155bez9fdbsaadc15f3"

sourceLocale
string
required

Source locale embedded in the XLIFF.

Example:

"en-US"

targetLocale
string
required

Target locale the XLIFF was translated into.

Example:

"de-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.

webhookUrl
string

Webhook URL you supplied in the request

requestId
string

Request ID you can use to retrieve the result