Skip to main content
POST
/
optimizely
/
v1
/
sync
/
convert-to-xliff
Convert stored raw Optimizely content to XLIFF synchronously
curl --request POST \
  --url https://eu.phrase.com/connectors/optimizely/v1/sync/convert-to-xliff \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "rawFiles": [
    {
      "storageId": "e48eda63928c4155bez9fdbsaadc15f3",
      "info": {
        "name": "item-12345.json"
      }
    }
  ],
  "sourceLocale": "en"
}
'
{
  "storageId": "e48eda63928c4155bez9fdbsaadc15f3"
}

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
enum<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.

Available options:
ID,
OBJECT

Body

application/json

Request body for converting already-stored raw Optimizely content into XLIFF 2.0 without re-downloading from Optimizely.

​
rawFiles
object[]
required

List of stored raw files (each carrying its storageId and original metadata) to convert.

​
sourceLocale
string
required

Source locale of the content (Optimizely locale code).

Example:

"en"

Response

OK — JSON storageId envelope (returned when X-ResponseType=ID).

​
storageId
string