Skip to main content
Rate limits are enforced per API key and cap your request volume. If you exceed your per-minute, per-hour, or per-day ceiling, the call is rate limited.

Limits by plan

The discovery endpoints (GET /us/statutes/coverage and GET /us/statutes/divisions) cost no credits or one credit, but they still count against these rate limits. Coverage changes weekly, not hourly, so cache both rather than calling them on every request.

Handling a 429

When you exceed a limit the API returns 429 with a Retry-After header telling you how many seconds to wait. Respect it, and add exponential backoff so retries spread out under sustained pressure.
Smooth your request rate before you hit the ceiling. A small client-side delay between calls in a paging loop keeps you comfortably under the per-minute limit and avoids retries entirely.

Errors

Every status code and how to recover from it.
Last modified on September 6, 2026