Ashby · Rate Limits
Ashby Rate Limits
Ashby applies per-API-key rate limits across its JSON-RPC API. The default is a sliding-window limit applied per access key and per endpoint family; exceeded requests return HTTP 429 with a Retry-After header.
Ashby Rate Limits is the machine-readable rate-limit profile for Ashby on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 3 rate-limit definitions, measuring requests and events.
The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include HR, ATS, Recruiting, Rate Limiting, and Throttling.
3 Limits
Throttle: 429
HRATSRecruitingRate LimitingThrottling
Limits
Per API Key Default token
Sliding-window limit per API key; 429 returned with Retry-After when exceeded.
Listing / Search Endpoints token
List endpoints (candidate.list, application.list) carry tighter limits than item-level reads; paginate aggressively.
Webhook Delivery subscription
Outbound webhook deliveries are signed and retried on 5xx; receivers must respond within the platform timeout.
Policies
Backoff Strategy
Exponential backoff with jitter on 429; honor Retry-After.
Pagination
Use cursor-based pagination on .list endpoints rather than scanning all records.
Webhooks-First
Subscribe to events for change notification; reduce list polling.
Sources
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.