# Phrase Developer Hub: English API Reference Connectors

## Connectors

###  

- [Introduction](https://developers.phrase.com/en/api/connectors/introduction.md)

### Overview

- [Authentication](https://developers.phrase.com/en/api/connectors/authentication.md)

### API Documentation

#### Braze

- [Upload translated XLIFF synchronously](https://developers.phrase.com/en/api/connectors/braze/upload-translated-xliff-synchronously.md): 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.
- [Upload raw Braze multilingual content synchronously](https://developers.phrase.com/en/api/connectors/braze/upload-raw-braze-multilingual-content-synchronously.md): 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.
- [List Braze multilingual content synchronously](https://developers.phrase.com/en/api/connectors/braze/list-braze-multilingual-content-synchronously.md): List Braze multilingual content reachable from `path` under the supplied `configuration`. Use this for project setup, change detection, or to drive a UI picker.
- [Download Braze multilingual content as XLIFF synchronously](https://developers.phrase.com/en/api/connectors/braze/download-braze-multilingual-content-as-xliff-synchronously.md): Download Braze multilingual content as XLIFF 2.0, ready for translation. The connector applies its segmentation and serialization rules, including locale fallbacks across the source and target Braze locale codes.
- [Download raw Braze multilingual content synchronously](https://developers.phrase.com/en/api/connectors/braze/download-raw-braze-multilingual-content-synchronously.md): Download raw multilingual content from Braze without any connector-side conversion. The returned payload is Braze's native JSON representation of the content blocks / campaigns selected by `path` and `configuration`.
- [Convert stored raw Braze content to XLIFF synchronously](https://developers.phrase.com/en/api/connectors/braze/convert-stored-raw-braze-content-to-xliff-synchronously.md): Convert raw Braze content already in Phrase file storage to XLIFF 2.0, without re-downloading from Braze. Each entry in `rawFiles` references a stored file (`storageId`) plus the metadata the connector needs to segment correctly.
- [Convert stored XLIFF back to raw Braze content synchronously](https://developers.phrase.com/en/api/connectors/braze/convert-stored-xliff-back-to-raw-braze-content-synchronously.md): Convert a translated XLIFF (referenced by `storageId`) back into Braze's raw content format without writing it to Braze. The result is stored in Phrase file storage and returned as a `storageId` you can then push with `upload-raw-file`.
- [Upload translated XLIFF asynchronously](https://developers.phrase.com/en/api/connectors/braze/upload-translated-xliff-asynchronously.md): 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.
- [Upload raw Braze multilingual content asynchronously](https://developers.phrase.com/en/api/connectors/braze/upload-raw-braze-multilingual-content-asynchronously.md): 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.
- [List Braze multilingual content asynchronously](https://developers.phrase.com/en/api/connectors/braze/list-braze-multilingual-content-asynchronously.md): List Braze multilingual content reachable from `path` under the supplied `configuration`. Use this for project setup, change detection, or to drive a UI picker.
- [Download Braze multilingual content as XLIFF asynchronously](https://developers.phrase.com/en/api/connectors/braze/download-braze-multilingual-content-as-xliff-asynchronously.md): Download Braze multilingual content as XLIFF 2.0, ready for translation. The connector applies its segmentation and serialization rules, including locale fallbacks across the source and target Braze locale codes.
- [Download raw Braze multilingual content asynchronously](https://developers.phrase.com/en/api/connectors/braze/download-raw-braze-multilingual-content-asynchronously.md): Download raw multilingual content from Braze without any connector-side conversion. The returned payload is Braze's native JSON representation of the content blocks / campaigns selected by `path` and `configuration`.
- [Convert stored raw Braze content to XLIFF asynchronously](https://developers.phrase.com/en/api/connectors/braze/convert-stored-raw-braze-content-to-xliff-asynchronously.md): Convert raw Braze content already in Phrase file storage to XLIFF 2.0, without re-downloading from Braze. Each entry in `rawFiles` references a stored file (`storageId`) plus the metadata the connector needs to segment correctly.
- [Convert stored XLIFF back to raw Braze content asynchronously](https://developers.phrase.com/en/api/connectors/braze/convert-stored-xliff-back-to-raw-braze-content-asynchronously.md): Convert a translated XLIFF (referenced by `storageId`) back into Braze's raw content format without writing it to Braze. The result is stored in Phrase file storage and returned as a `storageId` you can then push with `upload-raw-file`.

#### Connectors

- [List available connectors](https://developers.phrase.com/en/api/connectors/connectors/list-available-connectors.md): Returns all Bifrost-compatible connectors you have configured.

#### Contentful

- [Upload xliff content synchronously](https://developers.phrase.com/en/api/connectors/contentful/upload-xliff-content-synchronously.md): Upload translated XLIFF back to Contentful. The connector parses the XLIFF, maps target-language segments back onto the original entries, and writes them to the target locale in the configured space.
- [Upload raw content synchronously](https://developers.phrase.com/en/api/connectors/contentful/upload-raw-content-synchronously.md): Upload raw entry content back to Contentful for a given target locale. The request body must reference an already-stored file by `storageId` — upload the file to Phrase file storage first.
- [List content synchronously](https://developers.phrase.com/en/api/connectors/contentful/list-content-synchronously.md): List Contentful entries (and optionally referenced assets) reachable from `path` under the supplied `configuration`. Use this for project setup, change detection, or to drive a UI picker.
- [Download xliff content synchronously](https://developers.phrase.com/en/api/connectors/contentful/download-xliff-content-synchronously.md): Download Contentful entries as XLIFF 2.0, ready for translation. The connector applies its segmentation and serialization rules (rich-text handling, reference inlining, locale fallbacks).
- [Download raw content synchronously](https://developers.phrase.com/en/api/connectors/contentful/download-raw-content-synchronously.md): Download raw entry content from Contentful without any connector-side conversion. The returned payload is Contentful's native JSON representation of the entries selected by `path` and `configuration`.
- [Convert raw content from Contentful to XLIFF synchronously](https://developers.phrase.com/en/api/connectors/contentful/convert-raw-content-from-contentful-to-xliff-synchronously.md): Convert raw Contentful content already in Phrase file storage to XLIFF 2.0, without re-downloading from Contentful. Each entry in `rawFiles` references a stored file (`storageId`) plus the metadata the connector needs to segment correctly.
- [Convert an XLIFF file from the connector to a raw file used by Contentful synchronously](https://developers.phrase.com/en/api/connectors/contentful/convert-an-xliff-file-from-the-connector-to-a-raw-file-used-by-contentful-synchronously.md): Convert a translated XLIFF (referenced by `storageId`) back into Contentful's raw entry format without writing it to Contentful. The result is stored in Phrase file storage and returned as a `storageId` you can then push with `upload-raw-file`.
- [Upload xliff content asynchronously](https://developers.phrase.com/en/api/connectors/contentful/upload-xliff-content-asynchronously.md): Upload translated XLIFF back to Contentful. The connector parses the XLIFF, maps target-language segments back onto the original entries, and writes them to the target locale in the configured space.
- [Upload raw content asynchronously](https://developers.phrase.com/en/api/connectors/contentful/upload-raw-content-asynchronously.md): Upload raw entry content back to Contentful for a given target locale. The request body must reference an already-stored file by `storageId` — upload the file to Phrase file storage first.
- [List content asynchronously](https://developers.phrase.com/en/api/connectors/contentful/list-content-asynchronously.md): List Contentful entries (and optionally referenced assets) reachable from `path` under the supplied `configuration`. Use this for project setup, change detection, or to drive a UI picker.
- [Download xliff content asynchronously](https://developers.phrase.com/en/api/connectors/contentful/download-xliff-content-asynchronously.md): Download Contentful entries as XLIFF 2.0, ready for translation. The connector applies its segmentation and serialization rules (rich-text handling, reference inlining, locale fallbacks).
- [Download raw content asynchronously](https://developers.phrase.com/en/api/connectors/contentful/download-raw-content-asynchronously.md): Download raw entry content from Contentful without any connector-side conversion. The returned payload is Contentful's native JSON representation of the entries selected by `path` and `configuration`.
- [Convert raw content from Contentful to XLIFF asynchronously](https://developers.phrase.com/en/api/connectors/contentful/convert-raw-content-from-contentful-to-xliff-asynchronously.md): Convert raw Contentful content already in Phrase file storage to XLIFF 2.0, without re-downloading from Contentful. Each entry in `rawFiles` references a stored file (`storageId`) plus the metadata the connector needs to segment correctly.
- [Convert an XLIFF file from the connector to a raw file used by Contentful asynchronously](https://developers.phrase.com/en/api/connectors/contentful/convert-an-xliff-file-from-the-connector-to-a-raw-file-used-by-contentful-asynchronously.md): Convert a translated XLIFF (referenced by `storageId`) back into Contentful's raw entry format without writing it to Contentful. The result is stored in Phrase file storage and returned as a `storageId` you can then push with `upload-raw-file`.

#### Files

- [Upload file to file storage synchronously](https://developers.phrase.com/en/api/connectors/files/upload-file-to-file-storage-synchronously.md): Upload file synchronously to the file storage. The file is saved and can be retrieved by sending a GET request to this endpoint. The returned ID can be used as a parameter for uploading files to third party systems or for file conversion. The file will be deleted after 1 day.
- [Upload file to file storage asynchronously](https://developers.phrase.com/en/api/connectors/files/upload-file-to-file-storage-asynchronously.md): Upload file asynchronously to the file storage. The file is saved and can be retrieved by sending a GET request to this endpoint. The returned ID can be used as a parameter for uploading files to third party systems or for file conversion. The file will be deleted after 1 day.
- [Download file from file storage synchronously](https://developers.phrase.com/en/api/connectors/files/download-file-from-file-storage-synchronously.md): Download file synchronously from the file storage.

#### GitHub

- [Upload raw content synchronously](https://developers.phrase.com/en/api/connectors/github/upload-raw-content-synchronously.md)
- [Batch upload raw files synchronously — single commit via Git Blob/Tree API](https://developers.phrase.com/en/api/connectors/github/batch-upload-raw-files-synchronously-—-single-commit-via-git-blobtree-api.md)
- [List content synchronously](https://developers.phrase.com/en/api/connectors/github/list-content-synchronously.md)
- [Download raw content synchronously](https://developers.phrase.com/en/api/connectors/github/download-raw-content-synchronously.md)
- [Upload raw content asynchronously](https://developers.phrase.com/en/api/connectors/github/upload-raw-content-asynchronously.md)
- [Batch upload raw files asynchronously — single commit via Git Blob/Tree API](https://developers.phrase.com/en/api/connectors/github/batch-upload-raw-files-asynchronously-—-single-commit-via-git-blobtree-api.md)
- [List content asynchronously](https://developers.phrase.com/en/api/connectors/github/list-content-asynchronously.md)
- [Download raw content asynchronously](https://developers.phrase.com/en/api/connectors/github/download-raw-content-asynchronously.md)

#### Google Drive

- [Upload raw file bytes to Google Drive (streaming, phase 2)](https://developers.phrase.com/en/api/connectors/google-drive/upload-raw-file-bytes-to-google-drive-streaming-phase-2.md): Phase 2 of the streaming upload flow. The caller PUTs raw bytes to this endpoint after initializing a streaming upload via `POST /google-drive/v1/sync/upload-raw-file` with `X-Upload-Mode: STREAM`.
- [Upload raw content to Google Drive synchronously](https://developers.phrase.com/en/api/connectors/google-drive/upload-raw-content-to-google-drive-synchronously.md): Upload a raw binary file to Google Drive. Two delivery modes are supported via `X-Upload-Mode`:
- [List Google Drive content synchronously](https://developers.phrase.com/en/api/connectors/google-drive/list-google-drive-content-synchronously.md): List folders and files reachable from `path` in Google Drive. Use this for project setup, change detection, or to drive a UI picker.
- [Download raw content from Google Drive synchronously](https://developers.phrase.com/en/api/connectors/google-drive/download-raw-content-from-google-drive-synchronously.md): Download a raw binary file from Google Drive without any connector-side conversion. The returned payload is the original file bytes as stored in Drive (Docs/Sheets/Slides are exported as their native binary equivalents when applicable).
- [Upload raw content to Google Drive asynchronously](https://developers.phrase.com/en/api/connectors/google-drive/upload-raw-content-to-google-drive-asynchronously.md): Upload a raw binary file to Google Drive. Two delivery modes are supported via `X-Upload-Mode`:
- [List Google Drive content asynchronously](https://developers.phrase.com/en/api/connectors/google-drive/list-google-drive-content-asynchronously.md): List folders and files reachable from `path` in Google Drive. Use this for project setup, change detection, or to drive a UI picker.
- [Download raw content from Google Drive asynchronously](https://developers.phrase.com/en/api/connectors/google-drive/download-raw-content-from-google-drive-asynchronously.md): Download a raw binary file from Google Drive without any connector-side conversion. The returned payload is the original file bytes as stored in Drive (Docs/Sheets/Slides are exported as their native binary equivalents when applicable).

#### Optimizely

- [Upload translated XLIFF synchronously](https://developers.phrase.com/en/api/connectors/optimizely/upload-translated-xliff-synchronously.md): Upload translated XLIFF back to Optimizely. The connector parses the XLIFF, maps target-language segments back onto the original content items, and writes them to the target locale in the configured project.
- [Upload raw Optimizely content synchronously](https://developers.phrase.com/en/api/connectors/optimizely/upload-raw-optimizely-content-synchronously.md): 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.
- [List Optimizely content items synchronously](https://developers.phrase.com/en/api/connectors/optimizely/list-optimizely-content-items-synchronously.md): List Optimizely content items reachable from `path` under the supplied `configuration`. Use this for project setup, change detection, or to drive a UI picker.
- [Download Optimizely content as XLIFF synchronously](https://developers.phrase.com/en/api/connectors/optimizely/download-optimizely-content-as-xliff-synchronously.md): Download Optimizely content as XLIFF 2.0, ready for translation. The connector applies its segmentation and serialization rules to produce a translation-ready file targeting the requested locale pair.
- [Download raw Optimizely content synchronously](https://developers.phrase.com/en/api/connectors/optimizely/download-raw-optimizely-content-synchronously.md): Download raw content from Optimizely without any connector-side conversion. The returned payload is Optimizely's native representation of the content items selected by `path` and `configuration`.
- [Convert stored raw Optimizely content to XLIFF synchronously](https://developers.phrase.com/en/api/connectors/optimizely/convert-stored-raw-optimizely-content-to-xliff-synchronously.md): Convert raw Optimizely content already in Phrase file storage to XLIFF 2.0, without re-downloading from Optimizely. Each entry in `rawFiles` references a stored file (`storageId`) plus the metadata the connector needs to segment correctly.
- [Convert stored XLIFF back to raw Optimizely content synchronously](https://developers.phrase.com/en/api/connectors/optimizely/convert-stored-xliff-back-to-raw-optimizely-content-synchronously.md): Convert a translated XLIFF (referenced by `storageId`) back into Optimizely's raw content format without writing it to Optimizely. The result is stored in Phrase file storage and returned as a `storageId` you can then push with `upload-raw-file`.
- [Upload translated XLIFF asynchronously](https://developers.phrase.com/en/api/connectors/optimizely/upload-translated-xliff-asynchronously.md): Upload translated XLIFF back to Optimizely. The connector parses the XLIFF, maps target-language segments back onto the original content items, and writes them to the target locale in the configured project.
- [Upload raw Optimizely content asynchronously](https://developers.phrase.com/en/api/connectors/optimizely/upload-raw-optimizely-content-asynchronously.md): 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.
- [List Optimizely content items asynchronously](https://developers.phrase.com/en/api/connectors/optimizely/list-optimizely-content-items-asynchronously.md): List Optimizely content items reachable from `path` under the supplied `configuration`. Use this for project setup, change detection, or to drive a UI picker.
- [Download Optimizely content as XLIFF asynchronously](https://developers.phrase.com/en/api/connectors/optimizely/download-optimizely-content-as-xliff-asynchronously.md): Download Optimizely content as XLIFF 2.0, ready for translation. The connector applies its segmentation and serialization rules to produce a translation-ready file targeting the requested locale pair.
- [Download raw Optimizely content asynchronously](https://developers.phrase.com/en/api/connectors/optimizely/download-raw-optimizely-content-asynchronously.md): Download raw content from Optimizely without any connector-side conversion. The returned payload is Optimizely's native representation of the content items selected by `path` and `configuration`.
- [Convert stored raw Optimizely content to XLIFF asynchronously](https://developers.phrase.com/en/api/connectors/optimizely/convert-stored-raw-optimizely-content-to-xliff-asynchronously.md): Convert raw Optimizely content already in Phrase file storage to XLIFF 2.0, without re-downloading from Optimizely. Each entry in `rawFiles` references a stored file (`storageId`) plus the metadata the connector needs to segment correctly.
- [Convert stored XLIFF back to raw Optimizely content asynchronously](https://developers.phrase.com/en/api/connectors/optimizely/convert-stored-xliff-back-to-raw-optimizely-content-asynchronously.md): Convert a translated XLIFF (referenced by `storageId`) back into Optimizely's raw content format without writing it to Optimizely. The result is stored in Phrase file storage and returned as a `storageId` you can then push with `upload-raw-file`.

#### Tridion Docs

- [Upload raw Tridion content synchronously](https://developers.phrase.com/en/api/connectors/tridion-docs/upload-raw-tridion-content-synchronously.md): Upload raw content back to SDL Tridion for a given target locale. The request body must reference an already-stored file by `storageId` — upload the file to Phrase file storage first.
- [List Tridion items synchronously](https://developers.phrase.com/en/api/connectors/tridion-docs/list-tridion-items-synchronously.md): List Tridion items reachable from `path` under the supplied `configuration`. Use this for project setup, change detection, or to drive a UI picker.
- [Download raw Tridion content synchronously](https://developers.phrase.com/en/api/connectors/tridion-docs/download-raw-tridion-content-synchronously.md): Download raw content from SDL Tridion without any connector-side conversion. The returned payload is the native item content (typically XML) for the items selected by `path` and `configuration`.
- [Upload raw Tridion content asynchronously](https://developers.phrase.com/en/api/connectors/tridion-docs/upload-raw-tridion-content-asynchronously.md): Upload raw content back to SDL Tridion for a given target locale. The request body must reference an already-stored file by `storageId` — upload the file to Phrase file storage first.
- [List Tridion items asynchronously](https://developers.phrase.com/en/api/connectors/tridion-docs/list-tridion-items-asynchronously.md): List Tridion items reachable from `path` under the supplied `configuration`. Use this for project setup, change detection, or to drive a UI picker.
- [Download raw Tridion content asynchronously](https://developers.phrase.com/en/api/connectors/tridion-docs/download-raw-tridion-content-asynchronously.md): Download raw content from SDL Tridion without any connector-side conversion. The returned payload is the native item content (typically XML) for the items selected by `path` and `configuration`.

## OpenAPI Specs

- [phrase-connectors](/openapi/phrase-connectors.json)