Tito · Rate Limits

Tito Rate Limits

Tito does not publish fixed numeric rate limits for the Admin API in its public documentation. The documentation does define pagination behavior for collection endpoints: results are returned in pages via the page[number] and page[size] query parameters, with a default page size of 100 and a maximum page size of 1000, and pagination metadata (current_page, next_page, total_pages, total_count, per_page, overall_total) returned in a meta object. Clients should paginate large result sets rather than attempting to pull all records in a single request, and should handle throttling defensively.

Tito Rate Limits is the machine-readable rate-limit profile for Tito on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 2 rate-limit definitions, measuring requests and records.

The profile also includes 2 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Event Ticketing, Ticketing, Rate Limiting, and Quotas.

2 Limits Throttle: 429
Event TicketingTicketingRate LimitingQuotas

Limits

Admin API Requests account
requests
not published
No fixed numeric request-rate limit is documented for the Admin API.
Collection Page Size request
records
1000 max (default 100)
Set via page[size]; use page[number] to paginate. Default page size is 100, maximum 1000.

Policies

Pagination
Enumerating endpoints are paginated; iterate with page[number] and read next_page/total_pages from the meta object.
Backoff Strategy
On a 429 response, implement exponential backoff with jitter and honor any Retry-After header before retrying.

Sources