TicketSpice · Rate Limits

Ticketspice Rate Limits

The TicketSpice programmable surface is the shared Webconnex v2 Public REST API, which publishes fixed numeric rate limits enforced per account (per API key). There is a daily cap of 10,000 requests (reset at 00:00 UTC) and a burst cap of 900 requests per rolling 15-minute window. Search endpoints page results with a startingAfter cursor and a limit parameter that defaults to 50 records per page. Remaining capacity is reported in response headers, and requests over the limit are rejected with an HTTP 429.

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

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

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

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

3 Limits Throttle: 429
Event TicketingTicketingWebconnexRate LimitingQuotas

Limits

Daily Requests account
requests · day
10000
Resets at 00:00 UTC. Remaining reported via X-Daily-Remaining.
Burst Requests account
requests · 15 minutes
900
Rolling 15-minute window. Remaining reported via X-Burst-Remaining.
Search Page Size request
records
50 default
Controlled by the limit parameter; startingAfter provides cursor pagination. Some docs cite up to 250 max.

Policies

Cursor Pagination
Search endpoints return pages ordered by id; pass startingAfter with the last id to fetch the next page until hasMore is false.
Backoff Strategy
On HTTP 429, honor the X-Retry-After header and apply exponential backoff with jitter.
Per-Key Enforcement
Limits are enforced per account API key, so parallel jobs sharing a key share the same daily and burst budget.

Sources