Zeal · Rate Limits

Zeal Hq Rate Limits

The Zeal API applies per-account request rate limits and returns HTTP 429 when a client exceeds them. Zeal documents rate limiting alongside idempotency and pagination in its API reference; specific numeric thresholds are not published and are not reconciled in this artifact. Bulk operations (for example bulk employee checks) and asynchronous report jobs are provided so consumers can avoid hitting per-request limits on high-volume payroll operations.

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

It captures 3 rate-limit definitions, measuring requests, checks, and jobs.

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

Tagged areas include Payroll, Embedded Finance, Fintech, Rate Limiting, and Quotas.

3 Limits Throttle: 429
PayrollEmbedded FinanceFintechRate LimitingQuotasThrottling

Limits

Requests Per Account account
requests
see provider documentation
Per-account request rate limit; exact threshold and window not published.
Bulk Employee Checks account
checks
batched per bulk request
Use POST /employeeCheck/bulk to submit many checks in one call and reduce request volume.
Report Jobs account
jobs
asynchronous
Reports run as async jobs; poll job status rather than re-requesting synchronously.

Policies

Idempotency
Supply an idempotency key on create operations so retries after 429 or network errors do not duplicate payroll actions.
Backoff Strategy
Clients should implement exponential backoff with jitter on 429 responses and honor any Retry-After header.
Test Mode First
Exercise high-volume flows against a test API key before running them in production to avoid throttling live payroll runs.

Sources