--- title: "Connect Granola with an API key" method: POST path: "/v1/integrations/granola/connect" tags: ["integrations"] --- # Connect Granola with an API key `POST /v1/integrations/granola/connect` Connect Granola using a customer-provided API key. Every call creates an installation, also for a key already connected, e.g. the same notes feeding a second store. To replace an existing installation's key, e.g. after it expired, use `POST /v1/integrations/granola/installations/{installation_id}/reconnect` instead: connecting the new key would add an installation next to the old one. ## Request body - GranolaManualConnectBody — Request body for connecting Granola with an API key. - `api_key` string, required — Granola API key - `store_name` string, nullable — Ingestion store name. A store that already exists is shared: every data source connected to it ingests into it, except another installation of the same account, which would ingest every item again. Without it, the account's default store, numbered past a store another installation of the account feeds. Rejected with 422 when the connect refreshes an existing installation and names a store other than its own. - `new_store` boolean — Ingest into a store created for this connection: the connect fails with 409 when `store_name` names a store that already exists, and without `store_name` the default name is numbered past existing stores. Rejected with 422 when the connect refreshes an existing installation, which keeps its store. - `store_config` IntegrationStoreConfig — Store and file configuration chosen when connecting a data source. Applied to the ingestion store when the connector creates it and to every imported file. The defaults (contextualization on, high-quality ingestion) give the best retrieval quality and downstream availability. A pre-existing store keeps its own configuration; only the ingestion mode still applies to newly imported files. - `metadata_contextualization` boolean — Contextualize chunks with the connector's curated metadata fields - `file_contextualization` boolean — Generate an LLM context for each chunk situating it within the full document - `ingestion_mode` 'fast' | 'high_quality' — Strategy for adding a file to a store. - `sync_schedule_interval` 'off' | 'ten_minutes' | 'hourly' | 'daily' | 'weekly' — Initial periodic sync interval - `account_name` string, nullable — Name of the person the API key belongs to - `account_email` string, nullable — Email of the person the API key belongs to ## Response `200` The connected Granola installation - ConnectorInstallationResponse — Response containing one connected account. - `data` ConnectorInstallation, required — A connected account and the store it feeds, described the same way for every connector. - `installation_id` string, required — Installation ID - `provider` 'google_drive' | 'gmail' | 'slack' | 'granola', required — Connector provider - `status` string, required — Installation status - `account` ConnectorAccount, required — The third-party account an installation is authorized as. - `id` string, required — Provider-side account identifier (email, user ID, or team ID) - `name` string, nullable — Human-readable account name - `email` string, nullable — Account email, when the provider exposes one - `workspace` string, nullable — Workspace or organization the account belongs to, for providers that have one - `store_id` string, nullable — Store the installation ingests into - `store_name` string, nullable — Name of that store - `sync` ConnectorInstallationSync — Account-level sync facts: how many resources are in error, and the last failure of an account-wide job. - `failed_resource_count` integer — Resources whose last sync job failed - `last_error` string, nullable — Last failure of a job covering the whole account, such as a changes sync - `last_error_operation` string, nullable — Which account-wide job failed - `last_error_at` string, date-time, nullable — When it failed ## Other responses - `409` — The store already receives data from another installation of the same account, `new_store` names a store that already exists, a Slack workspace bot is already installed by a different Mixedbread organization, or a Notion internal integration that is already connected is asked for a new or different store - `422` — The request failed validation, the credentials it carries were rejected, or `new_store` is set on a connect that refreshes an existing installation ## Changes - **2026-09-26** `9c6c72afde2d` — 1 info - added the new optional request property `new_store` - **2026-09-21** `b12f43c90ba3` — 2 warning - added the new `bucket_unavailable_error` enum value to the `code/anyOf[subschema #1: ErrorCode]/` response property for the response status `409` - added the new `bucket_unavailable_error` enum value to the `code/anyOf[subschema #1: ErrorCode]/` response property for the response status `422` - **2026-09-15** `957bf8ec8df8` — 2 warning - added the new `store_frozen_error` enum value to the `code/anyOf[subschema #1: ErrorCode]/` response property for the response status `409` - added the new `store_frozen_error` enum value to the `code/anyOf[subschema #1: ErrorCode]/` response property for the response status `422` - **2026-09-10** `adde8ecfa74f` — 1 warning, 4 info - removed the optional property `detail` from the response with the `422` status - added the non-success response with the status `409` - added the required property `code` to the response with the `422` status - added the required property `message` to the response with the `422` status - …1 more - …earlier changes not shown [Full history](https://skmtc.dev/mixedbread/apis/mxbai-omni/changes/v1/integrations/granola/connect/post.md) --- [API](https://skmtc.dev/mixedbread/apis/mxbai-omni.md) · [All operations](https://skmtc.dev/mixedbread/apis/mxbai-omni/llms.txt) · [OpenAPI document](https://skmtc.dev/mixedbread/apis/mxbai-omni/revisions/9c6c72afde2d?raw)