Upload raw Optimizely content synchronously
Upload raw content back to Optimizely for a given target locale. 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 export). For
translated XLIFF, use upload-xliff-file.
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 raw content to Optimizely. The file must already be in Phrase file storage — reference it by storageId. Authenticate by supplying connectorUuid; the connector loads its stored credentials from TMS.
UUID of a connector instance configured in TMS.
"4282fec0-d2e9-4266-8733-3e634feb7b59"
Optimizely-specific behavior knobs.
Selector inside the Optimizely project — content item, folder, or ROOT.
Source locale of the stored file (Optimizely locale code).
"en"
Target locale to write into (Optimizely locale code).
"de"
Storage ID of the raw file (already uploaded to Phrase file storage) to push to Optimizely.
"e48eda63928c4155bez9fdbsaadc15f3"
Response
Success — the upload completed. The envelope reports success and any per-item errors returned by Optimizely (the connector accepts partial failures).