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, conforming to the API Commons Rate Limits specification.

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

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 Throttle: 429
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