Authorize Gmail
GET/v1/integrations/gmail/oauth/authorize
Authorization
Bearer token for API authentication. Format: `Bearer YOUR_API_KEY`
Query Parameters
Optional ingestion store name
Gmail installation ID when reconnecting an existing installation
trueContextualize chunks with the connector's curated metadata fields
trueGenerate an LLM context for each chunk situating it within the full document
high_qualityParsing strategy for imported files
Possible values
fasthigh_qualityResponse
307 with Location set to the provider's consent page. After consent the browser is redirected to the return URL registered on the organization's app, with these query parameters appended:
The connector: gmail
The installation that was created or reconnected. Present when `status` is `connected`.
Why consent failed. Present when `status` is `error`. Provider errors such as `access_denied` are passed through.
Possible values
access_deniedmissing_codeaccount_already_connectedreconnect_account_mismatchinvalid_statetoken_exchange_failedcallback_failedcurl -s -o /dev/null -w '%{redirect_url}' \
'https://api.mixedbread.com/v1/integrations/gmail/oauth/authorize?store_name=mail-olivia' \
-H 'Authorization: Bearer YOUR_API_KEY'# Location header of the 307: send the browser here
https://accounts.google.com/o/oauth2/v2/auth?client_id=…&redirect_uri=…&scope=…&access_type=offline&state=…
# Return URL after consent
https://platform.example.com/connected?provider=gmail&status=connected&installation_id=2f1c9a8e-6b4d-4e3a-9c1f-7d8e5b6a4c21
# Return URL when consent fails
https://platform.example.com/connected?provider=gmail&status=error&error=account_already_connected