Upload translated XLIFF synchronously
Upload translated XLIFF back to Braze. The connector parses the XLIFF, maps target-language segments back onto the original Braze content, and writes them to the target locale in the configured workspace.
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.
Body
Request body for uploading translated XLIFF back to Braze. Reference the stored XLIFF by storageId; the connector parses it and writes the target-locale segments to Braze.
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.
Source locale embedded in the XLIFF.
"en-US"
Target locale to write into.
"de-DE"
Storage ID of the translated XLIFF file (already uploaded to Phrase file storage).
"e48eda63928c4155bez9fdbsaadc15f3"
Response
Success — the XLIFF was parsed and written. The envelope reports success and any per-entry errors returned by Braze.