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.
Limits
Policies
Sources
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for rate limits
4 MCP tools reach this
find_rate_limitsBrowse and filter every rate limit in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/rate-limits/servicefusion-rate-limits"
curl "https://apis.io/api/v1/rate-limits?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.