Zcal Rate Limits
Zcal does not publish a general-purpose public REST API, and as a result there is no documented inbound API rate-limit policy (RPM / TPM / quotas) to reconcile. The primary programmatic surface is OUTBOUND webhooks, where Zcal POSTs booking lifecycle events to a subscriber URL you control; in that direction your own endpoint is the receiver, so any throughput limits are governed by the volume of bookings rather than an API quota. No public webhook delivery rate limit, retry schedule, or concurrency limit is documented at the sources reviewed.
Zcal Rate Limits is the machine-readable rate-limit profile for Zcal on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 2 rate-limit definitions, measuring requests and events.
The profile also includes 2 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include Scheduling, Calendar, Booking, Meetings, and Webhooks.
Limits
Policies
Sources
- https://help.zcal.co/integrations/webhooks
- https://help.zcal.co/integrations/webhooks/webhook-payload
- https://help.zcal.co/
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/zcal-rate-limits"
curl "https://apis.io/api/v1/rate-limits?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.