Zuper Rate Limits
Zuper does not publicly document specific rate limit thresholds in their developer portal as of June 2026. The API uses HTTPS with API key authentication via the x-api-key header. Rate limits are enforced server-side and vary by plan tier. Developers experiencing rate limit errors should contact Zuper support or consult the developer discussions forum at developers.zuper.co/discuss. A read-only API mode is available that returns 401 errors if write operations are attempted.
Zuper Rate Limits is the machine-readable rate-limit profile for Zuper on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 5 rate-limit definitions.
Tagged areas include Field Service Management, Scheduling, Dispatching, Invoicing, and Timesheets.
Limits
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/zuper-rate-limits"curl "https://apis.io/api/v1/rate-limits?limit=25"Discovery needs no key. Ratings and market analysis are Pro.