Rate limits - StatusStack Documentation

Versioned v1 operations share one limiter: 120 requests per minute. When you exceed it, the API returns 429 and a Retry-After header with the number of seconds until the window resets.

HTTP/1.1 429 Too Many Requests
Retry-After: 12
Content-Type: application/json

{
  "message": "Too Many Requests"
}

Retry after Retry-After seconds. Do not hammer the endpoint — wait, then resume at a steady rate.

What is limited

The v1-api limit applies to every operation in the v1 group: stacks, sources, website monitors, incidents, overrides, and the rest of the documented v1 surface. GET /health and /sso/discover are unversioned and are not part of that group.

MCP limits

MCP connections have two caps:

Per connection: 60 requests per minute by default across all authenticated MCP endpoints. The refusal is a JSON-RPC error -32000.
Per caller: an additional 120 requests per minute on the MCP routes, returned as { "message": "..." }.

MCP 429 responses are documented on each MCP endpoint.

Practical guidance

Cache list responses when you poll for dashboard-style views.
Prefer webhooks or the MCP tools for event-driven work instead of tight polling loops.
If you need a higher sustained rate, contact support@statusstack.com.