DICE · Pricing Plans

Dice Fm Plans Pricing

DICE does not sell its Ticket Holders API as a standalone, metered developer product. Access is a benefit of being a DICE partner (promoter, venue, or festival) that sells tickets through the DICE platform. Partners manage events and generate API tokens inside MIO (mio.dice.fm); the GraphQL API itself carries no separate published per-call price. DICE's underlying commercial model is ticketing: DICE earns a booking fee / commission on tickets sold, which appears in the API data as commission and diceCommission fields. Exact partner commercial terms are negotiated and not publicly reconciled here.

Dice Fm Plans Pricing is the machine-readable pricing-plan profile for DICE on the APIs.io network, conforming to the API Commons Plans specification.

It defines 2 plans, covering partner and usage tiers, with named plans including DICE Partner (API Access), DICE Ticketing Commission.

Tagged areas include Ticketing, Events, Partner API, GraphQL, and Plans.

2 Plans API Commons Plans
View Source
TicketingEventsPartner APIGraphQLPlans

Plans

DICE Partner (API Access) partner

API access is granted to onboarded DICE partners. Partners select events and generate a Bearer API token in MIO, then query their own events, tickets, orders, returns, transfers, and venues through the Ticket Holders GraphQL API. The API has no separate published fee; the commercial relationship is the ticketing agreement.

Partner API Access (contract · month) included with DICE partner agreement (no separate published API fee) USD
DICE Ticketing Commission usage

DICE's underlying revenue model on the platform is a booking fee / commission on each ticket sold. This is surfaced in the API as the commission and diceCommission fields on tickets and orders rather than as an API charge. Rates are set per partner agreement.

Per-Ticket Commission (tickets · month) per-ticket booking fee / commission (per partner agreement) USD

Sources