Skip to main content
POST
Send Bordereau Export Run to Google Drive

Authorizations

Authorization
string
header
required

User-principal OAuth 2.0 Bearer authentication. Send a user-scoped Auth0 access token (audience = the app API audience) as Authorization: Bearer <jwt>. The request resolves to the user's identity and is authorized by their Role on the {companyId} in the path — the same role-based permissions the web app enforces. This is the path the MCP connector uses to act on a user's behalf; endpoints that accept it list both BearerAuth and ApiKeyAuth.

Path Parameters

companyId
string<uuid>
required

Company identifier

runId
string<uuid>
required

The run identifier returned by POST /policies/bordereau/export-runs. Runs are scoped to their company AND their kind: a run id belonging to another company, or to an entity export run rather than a bordereau one, returns 404, exactly as an id that exists nowhere does.

Body

application/json
folderId
string
required

Google Drive folder ID in which to create the new spreadsheet.

Minimum string length: 1
googleOAuthToken
string
required

Google OAuth2 access token with write access to the target folder. The spreadsheet is created as this token's user, who owns the resulting file; the token is used once and never persisted.

Minimum string length: 1

Response

The run's file was delivered as a new spreadsheet

Result of delivering a succeeded export run's file to Google Drive as a new spreadsheet.

spreadsheetUrl
string<uri>
required

Direct URL to the created Google Sheets spreadsheet, in the caller's Drive.