Fountain · Rate Limits

Fountain Com Rate Limits

The Fountain Developer API enforces per-account rate limits to protect platform stability. Fountain does not publish specific numeric limits in its public reference; clients should page results (cursor / page + per_page), handle HTTP 429 responses, and back off. Bulk endpoints (bulk advance, bulk transitions, bulk booked-slots) exist to reduce request volume for high-throughput hiring operations.

Fountain Com Rate Limits is the machine-readable rate-limit profile for Fountain on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 3 rate-limit definitions, measuring requests, records, and results.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Hiring, Recruiting, Applicant Tracking, HR Tech, and Rate Limiting.

3 Limits Throttle: 429
HiringRecruitingApplicant TrackingHR TechRate LimitingQuotasThrottling

Limits

Requests Per Account account
requests
see provider documentation
Per-account request throttling; specific numeric limit not published.
Bulk Operations account
records
see provider documentation
Use bulk endpoints (advance, transitions, booked-slots) to reduce request count.
Pagination request
results
per_page
List endpoints support cursor- and page-based pagination via per_page.

Policies

Pagination
Use cursor or page + per_page to iterate large result sets rather than large single requests.
Backoff Strategy
On HTTP 429, implement exponential backoff with jitter and honor any Retry-After header.
Webhooks Over Polling
Subscribe to webhook-settings for hiring events instead of polling list endpoints.

Sources