Upload raw Braze multilingual content asynchronously
Upload raw multilingual content back to Braze. The request body must reference an
already-stored file by storageId — upload the file to Phrase file storage first.
Use this when you have non-XLIFF content (e.g. a manually edited content-block export).
For translated XLIFF, use upload-xliff-file.
Async variant. This endpoint returns immediately with { requestId, webHookUrl }. The actual 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 raw multilingual content to Braze. The file must already be in Phrase file storage — reference it by storageId. The connector loads stored credentials from TMS based on connectorUuid.
UUID of a connector instance configured in TMS.
"4282fec0-d2e9-4266-8733-3e634feb7b59"
Connector configuration for the Braze Multilang connector
{
"tags": ["marketing", "priority"],
"maxDaysFromLastUpdate": 30,
"includeHash": true
}Selector inside the Braze workspace — content block / campaign ID, or ROOT for the entire selection driven by configuration.
Storage ID of the raw file (already uploaded to Phrase file storage) to push to Braze.
"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.