Service Fusion · Rate Limits

Servicefusion Rate Limits

The Service Fusion Open API enforces a request-rate limit of approximately 60 requests per minute per account. Exceeding it returns HTTP 429; clients should honor Retry-After and back off. The API is available only on the Pro plan. Beyond the request cap, two operational constraints matter: list responses are paginated (pass page and per-page), and the /jobs list endpoint is known to hang when queried without a sort parameter, so all /jobs list requests should include a sort (for example sort=-start_date). The public API is read-and-create oriented - list, retrieve, and create are the reliably available operations - so there is limited update/delete surface to rate against.

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

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

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.

4 Limits Throttle: 429
Field Service ManagementFSMHome ServicesRate LimitingQuotas

Limits

API Requests account
requests
~60 per minute
Approximate per-account request-rate limit on the Open API; exceeding it returns 429.
Pagination Page Size request
records
per-page (bounded page size)
List endpoints are paginated via page and per-page query parameters.
Jobs List Sort Requirement endpoint
requests
sort parameter required
Unsorted /jobs list queries are known to hang; always pass a sort (e.g. sort=-start_date).
Plan Gating account
access
Pro plan only
API access is included only on the Service Fusion Pro subscription tier.

Policies

Backoff Strategy
On HTTP 429, honor the Retry-After header and apply exponential backoff with jitter before retrying.
Pagination
Iterate list results using page and per-page rather than requesting unbounded result sets.
Read and Create Oriented
The public API reliably supports list (GET), retrieve (GET), and create (POST); update (PUT) and delete (DELETE) are not consistently exposed.

Sources