DICE · Rate Limits

Dice Fm Rate Limits

DICE does not publish fixed numeric rate limits for the Ticket Holders GraphQL API. Access is partner-gated and scoped to the events a partner is authorized to see, so effective request behavior is governed by the partner token and the GraphQL query cost rather than a documented per-minute cap. Result volume is controlled through cursor-based pagination (first/after/before/last with PageInfo) instead of large unbounded responses.

Dice Fm Rate Limits is the machine-readable rate-limit profile for DICE on the APIs.io network, in the API Commons Rate Limits shape.

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

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 Ticketing, Events, Partner API, GraphQL, and Rate Limiting.

3 Limits Exhausted: HTTP 429
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
TicketingEventsPartner APIGraphQLRate LimitingQuotas

Limits

GraphQL API Requests token
requests
not published
No fixed numeric request-rate limit is documented for the Ticket Holders GraphQL API.
Query Result Pagination query
records
cursor-paginated
Connections are paged with first/after/before/last and PageInfo (endCursor, hasNextPage) rather than a global record cap.
Data Scope partner
events
partner-authorized
A token only returns data for events the partner is authorized to access in MIO.

Policies

Cursor Pagination
Use PageInfo.endCursor and hasNextPage to walk large result sets in bounded pages instead of requesting everything at once.
Backoff Strategy
Implement exponential backoff with jitter and honor Retry-After on any 429 or throttling response.
Coordinated Bulk Pulls
For large historical or backfill queries, use date-range filters (for example purchasedAt gte / returnedAt gte) and coordinate high-volume access with DICE.

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/dice-fm-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.