Tripleseat Rate Limits
Tripleseat enforces a documented rate limit of 10 requests per second on the Leads and Events endpoint families (including their .json, .xml, and /search variants). List endpoints paginate at 50 records per page via the page query parameter. Webhook delivery is retried: if a subscriber does not return HTTP 200, Tripleseat re-sends the same POST up to five additional times. Limits apply per API credential. Other endpoints are not documented with explicit per-second numbers.
Tripleseat Rate Limits is the machine-readable rate-limit profile for Tripleseat on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 4 rate-limit definitions, measuring requests_per_second and varies.
The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include Rate Limiting, Event Management, and Catering.
Limits
Policies
Sources
- https://support.tripleseat.com/hc/en-us/articles/212171807-API-Events-Endpoint
- https://support.tripleseat.com/hc/en-us/articles/212528787-API-Leads-Endpoint
- https://support.tripleseat.com/hc/en-us/articles/40075780832919-API-Webhooks
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.