[Cotlet](https://cotlet.dev/index.md) · [All integrations](https://cotlet.dev/integrations.md) · [MCP servers](https://cotlet.dev/integrations/mcp.md) · [APIs](https://cotlet.dev/integrations/api.md) · [API & MCP status](https://cotlet.dev/api-status.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Security](https://cotlet.dev/security.md) · [Custom API](https://cotlet.dev/custom-api.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# DICE API status Does DICE have an API or MCP server?

> DICE has a read-only Ticket Holders API for partners; no MCP server, Zapier app or webhooks found (checked 20 Nov 2026). Cotlet API & MCP access score: 2 out of 5. What exists instead, with sources.

Source: https://cotlet.dev/api-status/dice

DICE publishes a Ticket Holders API for its partners, "a GraphQL API that allows downstream systems to query on a number of entities related to a partner's events" (checked 20 November 2026). Its docs list queries only, and say: "API token can be generated in MIO and should be provided as authorization header." They do not say whether every promoter can make a token. No DICE MCP server, Zapier, Make or n8n app, webhooks or export page was found.

**Cotlet API & MCP access score: 2 out of 5.** A DICE promoter or venue can read its events, tickets and orders through the Ticket Holders API with code. No official route for ChatGPT or Claude to work in MIO was found.

Checked 20 Nov 2026 ·[How Cotlet scores](#how-cotlet-scores)·[Report an inaccuracy](mailto:contact@cotlet.dev?subject=DICE%20API%20status)

Cotlet publishes this page as an independent assessment. Cotlet is not affiliated with, endorsed by or sponsored by DICE. DICE is a trademark of its owner. If DICE's own tools cover what you need, use them first.

DICE API & MCP report

2/5

Cotlet API & MCP access score 2/10 points

Public API

2/3

MCP server

0/3

Zapier · Make · n8n

0/2

Webhooks

0/1

Data export

0/1

Checked

20 Nov 2026

[Report an inaccuracy](mailto:contact@cotlet.dev?subject=DICE%20API%20status) [How we score](#how-cotlet-scores)

Public API

Read only

2 of 3

MCP server

None

0 of 3

Zapier · Make · n8n

None found

0 of 2

Webhooks

None found

0 of 1

Data export

None found

0 of 1

On this page

1. [01 At a glance](#at-a-glance)
2. [02 API](#public-api)
3. [03 MCP server](#mcp-server)
4. [04 Zapier, Make, n8n](#automation)
5. [05 Export](#export)
6. [06 Routes](#routes)
7. [07 How Cotlet scores](#how-cotlet-scores)
8. [08 Sources](#sources)

01 · At a glance

## DICE API & MCP access at a glance

__DICE API & MCP access on 20 Nov 2026 2 of 10 points__
| Check | Points | Finding | Source |
| ------------------------- | ------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------ |
| Public API for businesses | 2 / 3 | Yes, read only: the Ticket Holders API for a partner's events, tickets, orders and ticket holders, with a token generated in MIO. Who can make a token is not stated | [\[1\]](#source-1) |
| Official MCP server | 0 / 3 | No DICE MCP server found on dice.fm or in the MCP Registry; the registry entries come from other publishers | [\[2\]](#source-2) |
| Zapier, Make, n8n | 0 / 2 | No DICE app found on Zapier, Make or n8n | [\[3\]](#source-3) |
| Webhooks | 0 / 1 | Webhooks are not mentioned in the Ticket Holders API docs | [\[1\]](#source-1) |
| Data export | 0 / 1 | No DICE help page about exporting sales or attendee data from MIO found | [\[4\]](#source-4) |

One more fact that earns no points: many fields of the Ticket Holders API are marked as available with restricted access, and the docs do not say how that access is granted ([DICE Ticket Holders API docs](https://partners-endpoint.dice.fm/graphql/docs/index.html)).

02 · API

## Does DICE have an API?

Read only

DICE publishes the Ticket Holders API for its partners: "a GraphQL API that allows downstream systems to query on a number of entities related to a partner's events." The docs list queries and no changes, and say: "API token can be generated in MIO and should be provided as authorization header." Who in MIO can make a token is not stated.

[ Source \[1\] · DICE: Ticket Holders API docs, version 1.0.0 ](#source-1)

03 · MCP server

## Does DICE have an MCP server?

None found

DICE: no MCP server found on dice.fm, and the official MCP Registry lists none from DICE (checked 20 November 2026). Its entries come from other publishers, some about a different company's jobs site.

[ Source \[2\] · Official MCP Registry, search for "dice", 20 Nov 2026: entries from other publishers ](#source-2)

04 · Zapier, Make, n8n

## Does DICE work with Zapier, Make or n8n?

None found

No DICE app was found on Zapier, Make or n8n on 20 November 2026; the Zapier and n8n pages return 404.

[ Source \[3\] · zapier.com/apps/dice/integrations and n8n.io/integrations/dice return 404; no DICE app found on make.com, 20 Nov 2026 ](#source-3)

05 · Export

## Can I export sales from DICE?

None found

DICE: no help page about exporting sales or attendee data from MIO was found on 20 November 2026\. The Ticket Holders API reads orders and ticket holders for partners with code.

[ Source \[4\] · DICE help center, searched 20 Nov 2026: no page on exporting sales or attendee data from MIO found ](#source-4)

06 · Routes

## How can I connect DICE to ChatGPT or Claude today?

A DICE business has two routes today, and they do different jobs.

mio.dice.fm Your DICE business account

1. Route 1  
### The Ticket Holders API  
Read only, with a token from MIO.

  - Event sales and orders: read, with code
  - Event changes: no
  - Ask in plain words: needs code
2. Route 2  
### [A cloud browser](https://cotlet.dev/integrations/dice-api-mcp-server.md)  
You sign in to your DICE business account in a browser that runs in the cloud, and your AI agent works on the screens you use: events, ticket sales, orders, door lists. Cotlet, which publishes this page, is a cloud browser of this kind.

  - Event sales and orders: with your login
  - Event changes: with your login
  - Ask in plain words: with your login

To connect your AI: [DICE MCP server](https://cotlet.dev/integrations/dice-api-mcp-server.md).

07 · How Cotlet scores

## How Cotlet scores API & MCP access

Cotlet scores one thing: how easily a business can connect its own software or AI agent to its own account. Five checks give up to 10 points, and the points give the Cotlet API & MCP access score, from 1 to 5.

Points to score

DICE · 2 points
1. 1 0 or 1
2. 2 2 to 4
3. 3 5 or 6
4. 4 7 or 8
5. 5 9 or 10

Where the 10 points come from

1. API 2 of 3
2. MCP 0 of 3
3. Zapier, Make, n8n 0 of 2
4. Webhooks 0 of 1
5. Data export 0 of 1

__How Cotlet scores API & MCP access: the five checks__
| Check | Points | What earns them |
| ------------------------------------- | ------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Official API for the business account | 0 to 3 | 3: public and self-serve, reads and writes. 2: public, but read only or on a higher plan. 1: by partner approval or as a paid add-on. 0: none |
| Official MCP server | 0 to 3 | 3: reads and writes the business account. 2: works on the business account, read only or limited. 1: exists, but not for the business account, such as an app in ChatGPT for clients. 0: none |
| Zapier, Make, n8n | 0 to 2 | 2: an app on two or more of them, with actions. 1: an app on one, or triggers only. 0: none |
| Webhooks | 0 or 1 | 1: documented webhooks for business events |
| Data export | 0 or 1 | 1: an official export, such as CSV, a report download or a data add-on |

__How Cotlet scores API & MCP access: points to score__
| Points | Score |
| ------- | ---------- |
| 9 or 10 | 5 out of 5 |
| 7 or 8 | 4 out of 5 |
| 5 or 6 | 3 out of 5 |
| 2 to 4 | 2 out of 5 |
| 0 or 1 | 1 out of 5 |

Every score rests on the sources listed on the page and carries the date it was checked. A score changes when the facts change. Cotlet sells a cloud browser that connects AI agents to web apps such as DICE, and says so on every page of this catalog.

08 · Sources

## Sources

1. \[1\]  
[DICE: Ticket Holders API docs, version 1.0.0](https://partners-endpoint.dice.fm/graphql/docs/index.html)  
partners-endpoint.dice.fm Checked 20 Nov 2026
2. \[2\]  
[Official MCP Registry, search for "dice", 20 Nov 2026: entries from other publishers](https://registry.modelcontextprotocol.io/v0/servers?search=dice)  
registry.modelcontextprotocol.io Checked 20 Nov 2026
3. \[3\]  
zapier.com/apps/dice/integrations and n8n.io/integrations/dice return 404; no DICE app found on make.com, 20 Nov 2026  
zapier.com, n8n.io, make.com Checked 20 Nov 2026
4. \[4\]  
DICE help center, searched 20 Nov 2026: no page on exporting sales or attendee data from MIO found  
dice.fm Checked 20 Nov 2026

## Something changed at DICE?

Write to contact@cotlet.dev and we recheck this page.

[Report an inaccuracy](mailto:contact@cotlet.dev?subject=DICE%20API%20status) [Connect DICE to your AI](https://cotlet.dev/integrations/dice-api-mcp-server.md)

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [MCP servers](https://cotlet.dev/integrations/mcp.md) · [APIs](https://cotlet.dev/integrations/api.md) · [API & MCP status](https://cotlet.dev/api-status.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md) · [Custom API](https://cotlet.dev/custom-api.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. [About us](https://cotlet.dev/about.md)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.
