Skip to main content
Every organization has two limits on /api/v1, both set by its plan:
  • a daily quota, counted per UTC day and reset at 00:00 UTC
  • a per-minute limit, counted per calendar minute
Both are counted per organization. Every API key in the organization draws from the same counters, so a second key does not add quota. The limits follow the organization’s current plan: an upgrade raises them for existing keys straight away, and a downgrade lowers them. Requests rejected by the per-minute limit do not count against the daily quota. Requests rejected by the daily quota are not counted either. Today’s usage against the quota is on the API keys page in the console.

Response headers

Every response under a limit carries the current state of that limit. Reset values are seconds until the window starts over. Enterprise organizations have no limits, so their responses carry none of these headers.

429 responses

A request over either limit returns 429 Too Many Requests with a Retry-After header (seconds) and a problem-detail body that names the limit and, when a larger plan exists, the upgrade:
limit.window is minute or day. Wait retry_after seconds before retrying; retrying sooner returns 429 again.

No API access

Keys belonging to an organization whose plan does not include the public API return 403 with title: "plan_does_not_permit_api". The key stays valid: upgrading restores access without rotating it.