Key limits and who can create keys
Not everyone in an organization can create keys, and the number of active keys is capped. These rules exist because every key can spend the organization’s money.
Who can create keys
| Role in the organization | Create keys | See and revoke keys |
|---|---|---|
| Owner | Yes | All keys in the organization |
| Administrator | Yes | All keys in the organization |
| Developer | Yes | Only keys they created |
| Other roles | No | — |
A member whose role can’t create keys sees “Your role cannot create API keys. Ask an organization admin.” An admin can create a key on their behalf.
Plan requirement
API keys need a paid plan. On the Free plan, key creation is refused with “Your account is a free one. Please upgrade to use the Syntic API.” If the plan exists but billing isn’t active, you’ll see “Your plan isn’t active. Please update your billing to use the Syntic API.”
How many keys
| Limit | Value | Message when reached |
|---|---|---|
| Active keys per member, per organization | 20 | ”You already have 20 active API keys in this organization. Revoke one before creating another.” |
| Active keys per organization | 100 | ”This organization already has 100 active API keys. Revoke unused keys before creating another.” |
Only active keys count. Revoking a key frees its slot straight away. Keys that Syntic Code creates for members also count toward the organization total.
Two-step verification
If you have two-step verification turned on, or your organization requires it for everyone, creating a key needs a session where you’ve entered your second-factor code. The Console always asks for it at sign-in, so this normally just works there.
Rate limit per key
Each key may send up to 600 requests per minute. Extra keys are not a way to raise this; ask for higher limits through Contact Sales → Increase Rate Limits. See Rate limits and quotas.