Tripleseat · Rate Limits

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.

4 Limits Throttle: 429
Rate LimitingEvent ManagementCatering

Limits

Leads endpoints key
requests_per_second · second
10
Applies to /v1/leads, /v1/leads.json, /v1/leads.xml, /v1/leads/search, /v1/leads/search.json, and /v1/leads/search.xml.
Events endpoints key
requests_per_second · second
10
Applies to /v1/events, /v1/events.json, /v1/events.xml, /v1/events/search, /v1/events/search.json, and /v1/events/search.xml.
Other endpoints key
varies
no explicit per-second limit documented
Pagination page size key
varies
50 records per page (page query parameter)

Policies

Pagination
Paginated list endpoints return 50 records per page; iterate using the page query parameter until the results array is empty.
Webhook retry
Subscribers must return HTTP 200 on receipt; otherwise Tripleseat re-sends the same webhook POST up to five additional times. Verify the X-Signature SHA256-HMAC header before processing.
Endpoint scoping
The 10 requests-per-second limit is scoped to the Leads and Events endpoint families specifically, not the API as a whole.

Sources