Greenhouse Rate Limits
Harvest v3 applies a fixed 30-second window per integration (custom and partner integrations are limited separately) with a separate 60-second window for token requests; the cap itself is not a published number -- it is read from X-RateLimit-Limit on every response (the docs example shows 75). 429 carries Retry-After. Legacy Harvest v1 uses a 10-second window, the Audit Log API 50 per 10 seconds (paginated 3 per 30 seconds), and Greenhouse Onboarding exposes a GraphQL rateLimit type.
Greenhouse Rate Limits is the rate-limit profile for Greenhouse on the APIs.io network — every limit transcribed verbatim from the provider’s own documentation on 2026-11-05.
It captures 3 rate-limit definitions, including Harvest v3 – per-integration fixed 30-second window — This limit is applied on a fixed-window basis, meaning the counter resets at the end of each 30-second interval.; Harvest v3 – access token requests — Requests to obtain a new access token are subject to a separate 60-second interval, enforced using the same fixed-window policy.; Harvest v3 – exhaustion — If you exceed the request limit within a 30-second window, the API will respond with an HTTP 429 Too Many Requests status code..
Limit state is signalled in the limit, remaining, reset, and retryAfter response headers, and an exhausted limit returns HTTP 429.
The profile also includes 1 backoff/retry policy defined and response codes documented for throttled.
Tagged areas include Human Resources, Greenhouse, Applicant Tracking, Recruiting, and Candidates.
limitremainingresetretryAfter
Limits
Policies
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.