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.
Limits
Policies
Sources
- https://docs.webconnex.io/api/v2/
- https://help.regfox.com/en/articles/2340089-rest-api
- https://fivetran.com/docs/connectors/applications/webconnex
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.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/rate-limits/ticketspice-rate-limits"
curl "https://apis.io/api/v1/rate-limits?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.