Skip to main content
Our API is currently for Enterprise customers only. Basic and Business users can use MCP to connect their notes to AI tools like Claude and ChatGPT.

Overview

What is the Granola Enterprise API?

The Enterprise API allows organizations to programmatically access meeting notes and transcripts that have been shared within workspace-wide folders. It enables use cases like CRM sync, knowledge base population, and custom integrations.

What endpoints are available?

The API currently has two endpoints:
  • GET /v0/notes - List all accessible notes with pagination
  • GET /v0/notes/{note_id} - Get detailed information about a specific note, including transcript and summary
For full API Documentation, please go here: https://docs.granola.ai/introduction

What data can I access through the API?

For each note, you can retrieve:
  • Note title and creation date
  • Owner information (name, email)
  • Calendar event details (title, invitees, organizer, start/end times)
  • Attendees list
  • Folder membership
  • AI-generated summary
  • Full transcript (with speaker identification and timestamps)

Access & Permissions

Can I access private meetings through the Enterprise API?

No. The Enterprise API only provides access to public notes - meetings that have been explicitly shared in a workspace-wide folder. Private meetings remain private. This is by design. People use Granola for sensitive conversations (one-on-ones, personal appointments, confidential discussions), and we believe this data should remain under individual control. If users wish to access their own personal notes, they can use the MCP and connect it to popular tools like Claude and ChatGPT.

Why can’t admins access all notes?

We take a privacy-first stance. Many users have personal or sensitive meetings in Granola that they wouldn’t want shared company-wide. Giving admin access to all private notes would undermine the trust users place in Granola. Alternative options:
  • Encourage your organization to share more notes in team folders by default
  • Use the MCP for individual users to access their own notes
  • Consider implementing default folders to automatically categorize notes

What’s the difference between the Enterprise API and the MCP?

FeatureEnterprise APIMCP
ScopeOrganization-wide public notesNotes the authenticated user created
AuthSingle API key for workspacePer-user OAuth
AccessPublic folder notes onlyOnly notes owned by the user
Use caseCRM sync, knowledge basePersonal AI assistants, Claude/ChatGPT

How do team folders work?

When you create a team folder, all members of your workspace can see notes in that folder. Notes shared to team folders become accessible via the Enterprise API. If a user moves a note into a team folder, it becomes public to the organization and accessible via the API.

Technical Questions

How does authentication work?

Use Bearer token authentication in your request headers:
Authorization: Bearer <your-api-key>
API keys can be generated by workspace administrators in Settings → API Keys and should be stored securely.

Is the API paginated?

Yes. The /v0/notes endpoint returns a maximum of 50 notes per request. Use the cursor parameter from the response to fetch additional pages.
{
  "notes": [...],
  "hasMore": true,
  "cursor": "eyJjcmVhdGVkX2F0Ijo..."
}

Can I filter notes by date?

Yes. Use these query parameters:
  • created_after - ISO 8601 date (e.g., 2024-01-01)
  • created_before - ISO 8601 date (e.g., 2024-12-31)

Can I filter notes by folder?

Not directly in v1. However, each note response includes folder_membership with folder IDs and names, so you can filter on your side after fetching.

How do I get transcripts?

Add ?include=transcript to the note detail endpoint:
GET /v0/notes/{note_id}?include=transcript

Are there rate limits?

Rate limits are applied per workspace to ensure fair usage and platform stability.
MetricValue
Burst capacity25 requests
Time window5 seconds
Sustained rate5 requests/second (300/minute)
When rate limits are exceeded, the API returns a 429 Too Many Requests response.

What’s the API versioning strategy?

The current version is v0 (alpha). Breaking changes may occur. When we release a stable version, we’ll maintain backwards compatibility.

Use Cases

Can I sync Granola notes to Hubspot or Salesforce?

Yes - this is one of the most common use cases. You can build a custom integration that:
  1. Periodically polls for new notes
  2. Matches attendees by email domain to your CRM contacts/accounts
  3. Creates activities or updates records in CRM
We’re exploring native Salesforce integration for a future release.

Can I build custom AI agents with Granola data?

Yes. Common patterns include:
  • Customer intelligence: Analyze sentiment across customer call transcripts
  • Product research: Query themes across hundreds of customer conversations
  • Personal assistants: Combine meeting data with other knowledge sources
The personal MCP will make this even easier for individual users.

What about real-time webhooks?

Not available in v1. Currently, you need to poll the API for new notes. Webhooks are on our roadmap based on customer demand.

Getting Started

How do I get an API key?

Workspace administrators can generate API keys directly in the Granola app by going to Settings → API Keys → Generate API Key. Each workspace can have up to 5 API keys. API access is included with Enterprise plans. If you need help or have questions, contact your Granola account manager or email hey@granola.so.

Is there a sandbox environment?

Not currently. We recommend testing with a small number of notes in a dedicated test folder.

Where can I get help?


Roadmap & Future

What’s coming next?

  • Personal MCP: OAuth-based access for individual users to all their notes
  • Webhook support: Real-time notifications when notes are created/updated
  • Native integrations: Salesforce, HubSpot, and other CRM platforms
  • Richer filtering: Filter by folder, attendee, or custom metadata

Will API access change pricing?

API access is included with Enterprise plans. We’ll provide notice if this changes.