Plans, limits & access
The API and webhooks are included for every workspace at no additional cost; keys are self-serve; the limits are the same for everyone.
API access and webhooks are included for every workspace at no additional cost. No approval or sales contact is needed: an Admin creates keys self-serve in Settings → API, and the key works the moment it is created.
What every workspace gets
- The full
/api/v1surface: workflows, runs, tasks, field values, comments, files, saved views, webhooks, schedules, automation rules, the member directory and CSV export — nothing is tier-gated. - Webhooks for every event type, with signed deliveries and retries.
- 600 requests per minute per key (a fixed 60-second window). Create separate keys for separate integrations; each has its own window.
- As many keys as you need, each with its own scopes, read-only flag and workflow or folder allowlist.
- Sandbox workspaces for testing (Sandbox workspaces).
Who can do what
| Action | Who |
|---|---|
| Create, rotate and revoke API keys | Admins, in Settings → API |
| Use a key | Anything that holds the secret — keys are not tied to a person's session |
| Manage webhooks | Builders and Admins in the app; any key with webhooks:manage through the API |
| Manage schedules | Builders and Admins in the app (Automations → Schedules); any key with schedules:manage |
| Manage automation rules | Builders and Admins in the app (Automations → Rules; a rule for every workflow is Admins only); any key with rules:manage (a rule for every workflow needs a key without an allowlist) |
| Flip a workspace to a sandbox | Admins, in Settings → API |
Keys outlive their creator: a key keeps working after the Admin who made it leaves the workspace — except for creating or changing a saved view, which needs the key's creator to still be a Builder or Admin. Revoke keys when their creator leaves.
Limits
Every limit is published on Limits and schedules; the rate limit is explained on Rate limits. There is no separate quota for webhooks.