Workiz · Rate Limits

Workiz Rate Limits

Workiz does not publish fixed numeric rate limits for its REST API. The API is gated behind the Developer API add-on and authenticated with an account API token placed in the request path, so throttling is applied per account. Errors, including throttling, are returned as JSON with HTTP status codes; clients should treat HTTP 429 as a throttle signal and back off. List endpoints (jobs, leads) are paginated via records and offset parameters, so large data pulls should page rather than request everything at once.

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

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

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

Tagged areas include Field Service Management, FSM, Home Services, Rate Limiting, and Quotas.

3 Limits Throttle: 429
Field Service ManagementFSMHome ServicesRate LimitingQuotas

Limits

REST API Requests account
requests
not published
No fixed numeric request-rate limit is documented for the Workiz REST API.
Job List Pagination account
records
configurable via records and offset
The /job/all/ endpoint returns paginated results controlled by the records and offset query parameters.
Lead List Pagination account
records
configurable via records and offset
The /lead/all/ endpoint returns paginated results controlled by the records and offset query parameters.

Policies

Backoff Strategy
On HTTP 429, back off with exponential delay and jitter before retrying.
Pagination
Use records and offset to page through large job and lead datasets instead of unbounded reads.
Add-On Gating
API access requires the Developer API add-on enabled from the Feature Center / Marketplace; disabling it revokes the token.

Sources