Skip to main content
POST
Download raw content from Google Drive 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.

X-ResponseType
enum<string>
default:ID

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
default:""
required

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

Example:

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

configuration
any
default:""
required

Connector configuration for this request. Currently unused, but reserved for future configuration flags.

Example:
path
object
locale
string
default:""

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"

{key}
any

Response

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

Binary file stream.