Public API Rate Limits
All Quiet now enforces rate limits on the Public API. Each API key is limited to 300 requests per 20 seconds and 2,700 requests per 5 minutes.
Published: Monday, 10 August 2026
All Quiet now enforces rate limits on the Public API to protect platform stability and ensure fair usage. Limits apply per API key — each key in your organization tracks its own quota independently.
Rate Limits
| Time window | Maximum requests |
|---|---|
| 20 seconds | 300 |
| 300 seconds (5 minutes) | 2,700 |
Both tiers apply simultaneously. When you exceed either limit, the API responds with HTTP 429 Too Many Requests and a message indicating which tier was exceeded.
What This Means for You
- Existing integrations: Most automation stays well within these limits. If you run high-frequency polling or bulk sync jobs, review your request patterns.
- Per API key: Each API key tracks its own quota. Requests authenticated with different keys are rate-limited independently.
- HTTP 429: When a limit is exceeded, retry after a short backoff. Both tiers are evaluated on every request.
Documentation
Full API details are available in our Swagger documentation:
More updates
-
New
Dynamic Incident Channels for Slack, MS Teams, and Mattermost
All Quiet can now automatically create dedicated incident channels in Slack, Microsoft Teams, and Mattermost. Configure triggers by severity, invite on-call members, and archive channels when incidents end.
-
New
Filter On-Call Report by Team
The on-call report now supports team-level filtering. Select one or more teams to calculate on-call hours for those teams only — in the web app and via the Public API.
Updated August 10, 2026