Download raw content from Google Drive synchronously

curl --request POST \
  --url https://eu.phrase.com/connectors/google-drive/v1/sync/download-raw-file \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "connectorUuid": "4282fec0-d2e9-4266-8733-3e634feb7b59",
  "configuration": {},
  "path": {
    "pathType": "FILE",
    "fileId": "1A2b3C4d5E6f7G8h9I0jK",
    "name": "report.pdf",
    "drive": {
      "driveType": "MY_DRIVE"
    },
    "parentChain": [
      {
        "id": "root",
        "name": "My Drive"
      }
    ]
  }
}
'

"<string>"

Google Drive

Download raw content from Google Drive synchronously

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

Use this when you need the source artefact intact (e.g. PDF, DOCX, image, video). Google Drive is a binary-file connector — there is no XLIFF or raw-to-XLIFF conversion endpoint.

Choosing sync vs async

/sync/download-raw-file blocks until the connector finishes. Use for small files and interactive callers. Subject to gateway timeouts (~60 s).
/async/download-raw-file returns immediately with a requestId and posts the result to the URL in X-Webhook when ready. Required for large files.

Response shape (sync only) is controlled by X-ResponseType:

ID (default) — JSON { "storageId": "..." }. The caller fetches the content from Phrase file storage later. Recommended for any non-trivial payload.
OBJECT — raw application/octet-stream. Faster for small payloads; the stream may be proxied directly from Drive with upstream Content-Type, Content-Disposition, and Content-Length headers preserved when available.

Response shape (this endpoint) is controlled by the X-ResponseType request header:

ID: returns JSON with a storageId referencing file storage (application/json)
OBJECT: returns a binary stream (application/octet-stream). Two variants:
- Streaming: proxied stream from the connector; status and headers (Content-Type, Content-Disposition, Content-Length) may come from upstream when present.
- File storage: Bifrost downloads from storage (single file or zip of multiple files) and returns application/octet-stream with Content-Disposition: attachment; filename="<actionId>".

POST

google-drive

sync

download-raw-file

Download raw content from Google Drive synchronously

curl --request POST \
  --url https://eu.phrase.com/connectors/google-drive/v1/sync/download-raw-file \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "connectorUuid": "4282fec0-d2e9-4266-8733-3e634feb7b59",
  "configuration": {},
  "path": {
    "pathType": "FILE",
    "fileId": "1A2b3C4d5E6f7G8h9I0jK",
    "name": "report.pdf",
    "drive": {
      "driveType": "MY_DRIVE"
    },
    "parentChain": [
      {
        "id": "root",
        "name": "My Drive"
      }
    ]
  }
}
'

"<string>"

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. (ID => JSON with storageId, OBJECT => binary stream).

Available options:

ID,

OBJECT

Body

application/json

Request payload for downloading a raw file from Google Drive through the connector.

Clients authenticate by referencing a stored connector via connectorUuid. The path describes which file or location to download from.

connectorUuid

string

required

UUID of a configured connector that holds stored Google Drive credentials.

Example:

"b9c06f76-4a44-4d2e-8a26-3d1e4b47e123"

configuration

object

required

Connector configuration for the Google Drive connector.

Currently no configuration options are exposed. The object is reserved for future configuration flags while keeping the API contract stable.

Example:

{}

path

object

Polymorphic description of a Google Drive location used by connector operations.

The pathType discriminator selects the concrete shape:

ROOT - connector entry listing available spaces
SHARED_DRIVES_ROOT - virtual root listing shared drives
FOLDER - real folder or drive root
FILE - real file under a folder

Option 1
Option 2
Option 3
Option 4

Show child attributes

locale

string

Locale code associated with the file content, if applicable. Optional. Use a BCP 47 or Phrase locale code (for example, "en", "de", "cs").

Example:

"en"

Response

OK (binary stream when X-ResponseType=OBJECT). Streaming may proxy upstream status/headers.

Binary file stream.

List Google Drive content synchronously Upload raw content to Google Drive asynchronously

⌘I