Bridge

Bridge runs Gmail, Google Drive, Slack, and Granola connections for your users under your own OAuth apps. Your backend calls the API with one organization API key; users consent on Google or Slack and return to your platform.

OAuth setup

Register your apps once per organization under Bridge → Apps in the dashboard. Each card's dialog shows the redirect URI, the scopes, and the Slack manifest to copy.

Gmail and Google Drive are separate apps: enter one Google client on both cards or a different client on each. A shared client needs both redirect URIs authorized. Publish the Google consent screen; an app left in Testing gets refresh tokens that expire after 7 days.

Return URL

The page on your platform where users land after consent, for example https://platform.example.com/connected (http://localhost is allowed for development). The callback appends these query parameters:

API reference

OAuth clients

Connect

Installations

Stores

Gmail

curl -s -o /dev/null -w '%{redirect_url}' \
  'https://api.mixedbread.com/v1/integrations/gmail/oauth/authorize?store_name=mail-42' \
  -H 'Authorization: Bearer YOUR_API_KEY'

curl https://api.mixedbread.com/v1/integrations/installations/INSTALLATION_ID \
  -H 'Authorization: Bearer YOUR_API_KEY'

{
  "data": {
    "installation_id": "2f1c9a8e-6b4d-4e3a-9c1f-7d8e5b6a4c21",
    "provider": "gmail",
    "status": "active",
    "account": { "id": "olivia@example.com", "name": "olivia@example.com", "email": "olivia@example.com", "workspace": null },
    "store_id": "5d3e7f9a-1b2c-4d6e-8f0a-9c8b7a6d5e4f",
    "store_name": "mail-42",
    "sync": { "failed_resource_count": 0, "last_error": null, "last_error_operation": null, "last_error_at": null }
  }
}

curl -X POST https://api.mixedbread.com/v1/integrations/installations/INSTALLATION_ID/sync \
  -H 'Content-Type: application/json' \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -d '{"sync_all": true}'

curl https://api.mixedbread.com/v1/integrations/installations/INSTALLATION_ID/resources \
  -H 'Authorization: Bearer YOUR_API_KEY'

curl -X PUT https://api.mixedbread.com/v1/integrations/installations/INSTALLATION_ID/resources \
  -H 'Content-Type: application/json' \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -d '{"resource_ids": ["INBOX", "Label_12"]}'

# installation status and account-level errors
curl https://api.mixedbread.com/v1/integrations/installations/INSTALLATION_ID \
  -H 'Authorization: Bearer YOUR_API_KEY'

# per-resource outcome in resources[].sync.last_run
curl https://api.mixedbread.com/v1/integrations/installations/INSTALLATION_ID/resources \
  -H 'Authorization: Bearer YOUR_API_KEY'

# resources whose last job failed
curl https://api.mixedbread.com/v1/integrations/installations/INSTALLATION_ID/resources/failed \
  -H 'Authorization: Bearer YOUR_API_KEY'

# files ingested so far, in file_counts
curl https://api.mixedbread.com/v1/stores/STORE_ID \
  -H 'Authorization: Bearer YOUR_API_KEY'

curl -X POST https://api.mixedbread.com/v1/stores/search \
  -H 'Content-Type: application/json' \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -d '{"query": "renewal terms", "store_identifiers": ["STORE_ID"], "top_k": 10}'

Google Drive

Same flow as Gmail with /v1/integrations/google_drive/oauth/authorize. Sync the whole Drive:

curl -X POST https://api.mixedbread.com/v1/integrations/installations/INSTALLATION_ID/sync \
  -H 'Content-Type: application/json' \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -d '{"sync_all": true}'

Differences:

• sync_all runs one job over the whole Drive, Shared with me included, and registers push notifications for changes. queued_resource_ids is empty and the root folders keep last_run: null; watch file_counts on the store instead.
• Resources are hierarchical: list a folder's children with ?parent_id=FOLDER_ID. Selecting a folder syncs its subtree.
• Files Drive cannot export (unsupported types, empty files) are skipped, not failed.
• Reconnect after needs_reauth by repeating step 1 with the same Google account.

Slack

Same flow with /v1/integrations/slack/oauth/authorize. Sync every conversation the user is in:

curl -X POST https://api.mixedbread.com/v1/integrations/installations/INSTALLATION_ID/sync \
  -H 'Content-Type: application/json' \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -d '{"sync_all": true}'

Differences:

• Users connect as themselves (access_mode=user, the default), each with their own installation and store. account.workspace holds the workspace name.
• sync_all covers every conversation the user is a member of: channels, private channels, group messages, and direct messages. Public channels they have not joined are skipped with not_a_member.
• Right after connecting, the conversation catalog is still being built: the listing reports listing_status: "loading" and sync_all is applied when the walk completes. Refresh Resources rebuilds the catalog later, for example after the user joins channels.
• New messages arrive through Slack events verified with the signing secret you registered.

Granola

No OAuth. Connect with the user's API key and state who it belongs to:

curl -X POST https://api.mixedbread.com/v1/integrations/granola/connect \
  -H 'Content-Type: application/json' \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -d '{
    "api_key": "GRANOLA_API_KEY",
    "account_name": "Olivia Chen",
    "account_email": "olivia@example.com",
    "store_name": "notes-42"
  }'

data.id is the installation id and data.metadata.granola_ingestion_store_id the store id; an invalid key returns 422. Sync every note:

curl -X POST https://api.mixedbread.com/v1/integrations/installations/INSTALLATION_ID/sync \
  -H 'Content-Type: application/json' \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -d '{"sync_all": true}'

Then monitor and search as in steps 4 and 5 of the Gmail flow. Differences:

• sync_all imports every note the key can see and polls every ten minutes. Change the cadence with Update Granola Schedule: off, ten_minutes, hourly, daily, or weekly.
• Resources are folders, listed hierarchically like Drive.
• Personal keys expire on Granola's side. The installation then records sync.last_error and the user connects again with a new key.

Disconnect

curl -X DELETE https://api.mixedbread.com/v1/integrations/installations/INSTALLATION_ID \
  -H 'Authorization: Bearer YOUR_API_KEY'

Stops the sync and revokes the grant at the provider. Google revokes the whole authorization for a client, so a Google grant is kept while another installation of the same account uses the same OAuth client, for example Gmail and Drive on one client. The store and its files remain; delete the store separately if the data should go too.