Skip to main content
POST
Upload translated XLIFF synchronously

Authorizations

Authorization
string
header
required

IDM-issued JWT. Obtain via the IDM authentication flow and pass as: Bearer

Headers

X-ActionId
string
default:""

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

application/json

Request body for uploading a translated XLIFF into one language of a Document360 article. The connector converts the XLIFF to the raw format and then writes it, as in upload-raw-file.

credentials
object
required

Connection holding the Document360 API key and host.

path
object
required

The article the translation is written to (ARTICLE with projectId and articleId).

sourceLocale
string
default:""
required

Source locale of the XLIFF (locale code, e.g. en).

Minimum string length: 1
Example:

"en"

targetLocale
string
default:""
required

Language to write into (locale code, e.g. de).

Minimum string length: 1
Example:

"de"

storageId
string
default:""
required

Storage ID of the translated XLIFF file (already in Phrase file storage).

Minimum string length: 1
Example:

"e48eda63928c4155bez9fdbsaadc15f3"

configuration
object

Document360 settings; may be omitted (connector defaults apply).

Example:
{key}
any

Response

Success — the XLIFF was parsed and written. The envelope reports success and any per-item errors returned by Document360.

success
boolean
errors
object[]
{key}
any