Docs · API
Rate limits
Per-org and per-API-key quotas — understand limits, handle 429s, and request increases.
Quotas
The REST API is rate-limited per organization and per API key using a sliding window. Health and readiness probes(/api/v1/health, /api/v1/ready)are exempt. Webhook delivery from GitHub is not counted against your API quota.
- Default: 120 requests / minute per API key.
- Memory recall (
POST /api/v1/memory/recall) is metered separately as it is compute-heavy. - Limits are advisory during early access and may be adjusted — contact support to raise them.
Reading the headers
Every response carries the current window state so you can throttle before hitting the limit:
response-headers.txt
HTTP/1.1 200 OK X-RateLimit-Limit: 120 X-RateLimit-Remaining: 118 X-RateLimit-Reset: 1753093451 # unix epoch when the window resets
Handling 429s
When you exceed the limit the API returns 429 with a Retry-After header. Wait that many seconds, then retry with exponential backoff and jitter:
429.txt
HTTP/1.1 429 Too Many Requests
Retry-After: 12
{
"detail": "Rate limit exceeded. Retry after 12s.",
"status": 429
}To request a higher quota, email support@driftguard.io with your org and expected request volume.