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, in the API Commons Rate Limits shape.

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

Limit state is signalled in the dailyRemaining, burstRemaining, and retryAfter response headers, and an exhausted limit returns HTTP 429.

This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.

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 Exhausted: HTTP 429 dailyRemainingburstRemainingretryAfter
Method: generated, dated 2026-07-05.
Written by API Evangelist on 2026-07-05 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
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

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.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/ticketspice-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.