Paychex · Rate Limits

Paychex Developer Rate Limits

Paychex enforces rate limits and pagination caps on its REST APIs but does not document specific thresholds publicly. Partners receive limits as part of their onboarding documentation; sandbox limits are smaller than production. Clients should implement backoff on 429 responses and respect the documented pagination caps (default 25, max 100 per page).

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

It captures 4 rate-limit definitions, measuring varies and items_per_page.

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

Tagged areas include Rate Limiting, Pagination, Paychex Flex, and Payroll.

4 Limits Throttle: 429
Rate LimitingPaginationPaychex FlexPayroll

Limits

Per-partner production rate limit account
varies
see Paychex partner documentation
Not publicly disclosed; obtained via partner onboarding.
Sandbox rate limit account
varies
lower than production
Sandbox environments are tuned for development traffic, not load testing.
Pagination default request
items_per_page
25
Default page size for list endpoints when limit is omitted.
Pagination max request
items_per_page
100
Maximum allowed page size for list endpoints.

Policies

Backoff
Use exponential backoff with jitter on 429/503 responses; honor Retry-After when present.
Sandbox vs production
Sandbox limits are smaller than production; do not load-test in sandbox.
Partner-scoped
Limits are scoped to the registered partner application credentials, not per end-client.
Pagination
Use offset/limit pagination; request large result sets in pages of no more than 100.

Sources