API Key Scopes
There are two types of API keys. Each key type uses its own set of routes:
- Personal keys use
/v1/me/ routes
- Workspace keys use
/v1/workspace/ routes
Using a key on the wrong route set will return a 403 error. Both route sets use the same request format — see Getting Started.
If you only need access to your own data, use a Personal key. Use a Workspace key when you need to query across all team members or filter by user.
Shared Meeting Access (Personal Keys)
Personal keys don’t just return your own meetings — they also include meetings that have been shared with you:
- Directly shared — Meetings explicitly shared with you by a teammate
- Shared via tags — Meetings tagged with a label that’s been shared with you
This applies to both meeting listing and task listing. Deleting meetings is restricted to meetings you own.
Rate Limiting
API requests are limited to 100 requests per minute.
- Personal keys — The limit applies per user. Each user with their own key gets their own quota.
- Workspace keys — The limit applies per workspace. All workspace keys share the same quota.
When you exceed the limit, you’ll receive a 429 Too Many Requests response with these headers:
Error Responses
All errors return a JSON object with an error field:
Status Codes
Common Error Examples
Missing API key:
Wrong key type for route:
No access to a meeting:
Invalid query parameter:
