Skip to main content
The Granola API lets you build custom integrations with programmatic access to meeting notes, transcripts, and AI summaries. When you create an API key, you choose which note access scopes it should include.

​
What can you build?

  • Custom AI agents - Build agents that analyze sentiment across your calls, surface recurring themes in product feedback, or combine meeting context with other data sources for deeper insights.
  • Knowledge bases & wikis - Feed meeting notes into Notion, Confluence, or a wiki so your team’s knowledge is searchable and current.
  • Task & follow-up automation - Extract action items from meeting notes and automatically create tasks in Linear, Jira, Todoist, or your project management tool of choice.
  • CRM sync and reporting - Push meeting summaries and action items to CRM records, dashboards, or internal reporting workflows.
If you just want to chat with your notes in Claude, ChatGPT or another LLM, you can also try the Granola MCP. MCP uses browser-based OAuth and is optimized for AI assistants.

​
Who is it for?

Any workspace member on a Business or Enterprise plan can create API keys. On Enterprise plans, workspace admins can control which note access scopes members can use in Settings → Workspace → General → API access for members.

​
Access scopes

Notes in Granola are private by default. For a note to appear through the public notes scope, it must be in a folder visible to everyone in your workspace, such as a folder in the Team space. Notes that remain in private folders are only available through personal notes access for users who can already access them.

​
Getting started

  1. Open the Granola desktop app
  2. Go to Settings → Connectors → API keys
  3. Click Create new key
  4. Select the note access scopes the key should include
  5. Click Generate API Key
  6. Copy your API key for use in other apps
On Enterprise plans, an admin may need to enable API access scopes before members can create keys for those scopes.

​
Managing API access on Enterprise

Workspace admins on Enterprise plans can choose which scopes members can use:
  1. Open Settings → Workspace → General
  2. Find API access for members
  3. Click Manage
  4. Choose which note access scopes members can use
This lets Enterprise workspaces allow personal notes access, public notes access, both, or neither.

​
Workspace API keys

Workspace API keys are managed by admins and belong to the workspace rather than an individual user. They’re available on Business and Enterprise plans, and unlike personal API keys they don’t expire and aren’t tied to anyone’s account — so they keep working even if the admin who created them leaves. A workspace API key can access:
  • Public notes — notes visible to everyone in the workspace, such as notes in the Team space. If an admin has turned off Allow public folders for the workspace, these notes aren’t exposed to the API.
  • Notes in spaces with API access enabled — a space’s notes can be read by workspace API keys when Allow Granola API access is turned on for that space, either when it’s created or later from Settings → Spaces. This exposes the notes in that space, including its folders and subfolders.
Workspace API keys can’t read private notes or folders that haven’t been explicitly shared in this way.
Allow Granola API access is turned on by default when you create a new space. If you don’t want a space’s notes to be readable by workspace API keys, turn it off when creating the space (or later in Settings → Spaces).
To create a workspace API key:
  1. Open the Granola desktop app
  2. Go to Settings → Connectors → Workspace API keys
  3. Click Create new key
  4. Copy your API key for use in other apps
Only workspace admins can create and manage workspace API keys.

​
Revoking a key

Personal and workspace API keys are managed on separate pages, so revoke each from its own page. To revoke a personal API key:
  1. Go to Settings → Connectors → API keys
  2. Find the key you want to revoke and click Revoke
  3. Confirm in the dialog
To revoke a workspace API key (admins only):
  1. Go to Settings → Connectors → Workspace API keys
  2. Find the key you want to revoke and click Revoke
  3. Confirm in the dialog
Once revoked, the key is permanently disabled and moves to the Revoked section of the table. This cannot be undone.

API Documentation

Full API reference with endpoints, authentication, and examples.

​
FAQs

You need a Business or Enterprise plan to create API keys.
The Granola API gives you an API key for scripts, automations, and custom integrations. MCP uses browser-based OAuth and is designed for conversational AI tools like Claude and ChatGPT.
Only if the key includes personal notes access and the key owner can already access those notes in Granola. Public notes access only includes notes visible to everyone in the workspace.
Yes. Select both Personal notes and Public notes when creating the key.
The API only returns notes that match the key’s access scopes. For public notes access, make sure the notes are in a folder visible to everyone in the workspace, such as a folder in the Team space. For personal notes access, make sure the key owner can access those notes in Granola.
Not currently. We recommend testing with a small number of notes in a dedicated test folder.
Yes. API keys are rate limited to 25 requests burst capacity with a sustained rate of 5 requests/second. Limits may apply per user or workspace depending on the key’s access scope.
Yes. Webhooks are available on Business and Enterprise plans. See the webhooks guide to register an endpoint, subscribe to events, verify signatures, and handle retries.