API Rate Limiting Goes Live: Per-User and Per-IP Limits With 429 Responses

· API · New Feature · All updates

API rate limiting is now active. Every authenticated API request is tracked both per user and per IP address, against configurable limits per minute and per hour.

01 What happens at the limit

Cross the threshold and the request returns a 429 response carrying a Retry-After header. The header tells you how long to wait; back off for that long and retry. Nothing is lost and no key is disabled.

API request Counted per user and per IP Under limit: served Over limit: 429 with Retry-After
Each authenticated request is counted twice — against the user and against the calling IP.

02 Exemptions and custom limits

  • Admin accounts are exempt. They are not rate limited.
  • Custom limits. An individual user or IP address can be given limits of its own.
  • Blocking. A user or IP can also be blocked entirely.

03 Usage over time

Monthly request counters are stored persistently, so your API usage can be reviewed across months rather than only in the current window.

API usage dashboard

More in API

View the full changelog