Get a weekly DICE ticket sales report with returns and transfers

1. Sign in to MIO, DICE's partner dashboard, open the first upcoming event and read its sales by ticket type.
2. Write down door and box office sales on their own line, because DICE's US self sign-up terms charge a separate 10% Box Office Fee on them.
3. Look up the tickets fans returned and the tickets they sent to friends for the same event, since both change who will stand at the door.
4. Repeat for every show on sale and copy the totals next to last week's row in the spreadsheet to see the change.
5. Every show on sale adds another screen to the Monday round, and a show that stopped selling mid-week is only noticed when someone compares the numbers by hand.

Every Monday, give me last week's DICE sales for every show on sale: tickets per ticket type, door and external sales apart, and the returns and transfers since last Monday.

1. 01

   Pick the shows that matter this week

   list_events with state approved and a start after today gives the shows on sale. Drafts, declined and cancelled events stay out. A show that ended last weekend appears once more with its final count, then drops off the next report.

2. 02

   Count last week next to the total

   get_sales_summary runs per show twice: with since set to last Monday 00:00 in the account's time zone, and without it for the running total. A show that sold 140 overall but 2 this week stands out at once.

3. 03

   Keep door, free and external apart

   Door and external lines, such as tickets sold through Fever, are reported apart from app sales. Free tickets count toward attendance but stay out of face value, so guest tickets do not inflate revenue.

4. 04

   Add who handed tickets back

   list_returns and list_transfers run once across all events with the same since. Each return is matched to its show and ticket type; a return for a show missing from this week's list is flagged, not dropped.

5. 05

   Flag, change nothing

   The agent marks shows that sold less than the week before and shows within 10% of their total allocation. It edits nothing in MIO; a new release or a price change is a separate request to you.

Week 5 to 11 Oct 2026, 4 shows on sale, 1 finished.
Club Night, 14 Nov: 64 sold this week, 182 of 350 in total. Early bird sold out, General admission 82.
Rooftop Session, 5 Dec: 9 this week, down from 31 the week before.
Late Lines, 10 Oct (final): 211 tickets, of which 22 door, 6 external, 3 free (not in face value).
Returns: 5 tickets on Club Night, reason "Can't make it" on 4 of them.
Transfers: 11 tickets sent to friends, 7 of them for Club Night.

• DICE's Ticket Holders API labels every order with one of four sales channels: INTERNET, DOOR, FREE or EXTERNAL, where EXTERNAL covers tickets sold by a third party such as Fever.
• DICE's US self sign-up terms charge a 10% Box Office Fee on box office and door sales, plus a 3% transaction fee on tickets sold through DICE box office terminals.
• A DICE fan who returns a ticket to the wait list gets money back only when another fan buys it; an unsold ticket goes back to the fan's account.
• The DICE wait list runs only on sold-out shows where the organiser switched it on, and under DICE's US self sign-up terms DICE alone sets each event's wait list deadline and wait list price.
• A DICE ticket can no longer be sent to a friend or returned to the wait list once the fan activates its QR code, which opens on show day, usually a couple of hours before the event starts.

Every tool here only reads, so it can run weekly from n8n, Make, Zapier or cron without waiting for your OK.

Sources: DICE Ticket Holders API reference · DICE Self Sign-Up Terms and Conditions USA · DICE Help: The wait list explained · DICE Help: How to activate your tickets on the day of the event

curl https://cotlet.dev/api/v1/dice/get_sales_summary \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"event_id":"ev_48213","since":"2026-10-05T00:00:00+01:00"}'

{
  "event_id": "ev_48213",
  "currency": "USD",
  "tickets_sold": 182,
  "face_value": 314000,
  "by_ticket_type": [
    {
      "ticket_type_id": "8841273",
      "name": "Early bird",
      "tickets": 100,
      "face_value": 150000
    },
    {
      "ticket_type_id": "8841290",
      "name": "General admission",
      "tickets": 82,
      "face_value": 164000
    }
  ],
  "by_channel": [
    {
      "channel": "internet",
      "tickets": 160,
      "face_value": 276000
    },
    {
      "channel": "door",
      "tickets": 22,
      "face_value": 38000
    }
  ]
}

MCP: add https://cotlet.dev/mcp/v1 with the same key; the tool is dice_get_sales_summary. Example data.

• Create a DICE event draft with ticket types
• Add a new DICE ticket release when early bird sells out
• Update a DICE event and message ticket holders
• DICE API and MCP server: every tool
• All use cases