# Update a DICE event and message ticket holders

> Doors moved or the venue changed? Update the DICE event in MIO and send ticket holders one MIO Connect message, kept to event information.

Source: https://cotlet.dev/integrations/dice-api-mcp-server/announce-event-change

The support act pulls out on Thursday, doors move to 20:00, or the show moves to a bigger room. The event in MIO has to change first, then everyone holding a ticket has to hear it before they set off.

Cotlet does it in your own DICE account with get\_event, update\_event and message\_attendees, called by your AI agent, an n8n workflow or a script.

[Request access](https://cotlet.dev/app/signup?app=dice) [All DICE tools](https://cotlet.dev/integrations/dice-api-mcp-server)

Hosted · nothing to install or maintain

Official options

## Can DICE do this on its own?

DICE has no API to edit events or message fans (checked 12 Oct 2026); its Ticket Holders API only reads. DICE does handle part of a reschedule itself: it emails ticket holders and updates their tickets once a new date is confirmed. Door times, set times, a room change or a lost support act are not reschedules, and for those the promoter writes and sends a MIO Connect message by hand.

By hand

## How you do it in DICE today

1. Sign in to MIO, open the event and edit the times, venue or line-up; DICE's terms ask promoters to make scheduling, venue and line-up changes in MIO without undue delay.
2. Open MIO Connect and write one message to the fans attending, limited to what they need to know about this event.
3. For a new date, reschedule the event: DICE then marks it on the tickets, emails all ticket holders and updates the app once the new date is confirmed.
4. Expect refund requests after a reschedule, because DICE fans who cannot make the new date can ask for their money back, and the promoter funds those refunds.
5. Under time pressure the edit and the message drift apart: the app says 21:00 while the message says 20:00, or a line-up note goes out with a plug for next month's show, which MIO Connect does not allow.

With an agent

## How to update a DICE event and message ticket holders

Prompt

```
Doors for Club Night moved from 22:00 to 20:00. Update the event and tell everyone with a ticket that their ticket is still valid.
```

1. 01  
### Tell a change from a reschedule  
get\_event shows the current date, times, venue and line-up. A move to another day is a reschedule with refund consequences, so the agent stops and asks you before touching the date. Same-day time, room or line-up changes go ahead.
2. 02  
### Edit only what changed  
update\_event receives just the changed fields, for example start moved from 22:00 to 20:00 in the venue's time zone. The agent reads the event back and compares it with your request before any message is drafted.
3. 03  
### Write one operational message  
The draft states the change, the new time or place and that tickets stay valid. The agent cuts anything MIO Connect forbids, such as discounts, other events, merch, surveys or prompts to update marketing preferences, and tells you what it cut.
4. 04  
### Send once, with your OK  
message\_attendees waits for your confirmation and cannot be unsent. After a timeout the agent checks the result instead of sending again, so no fan gets the same notice twice.
5. 05  
### Report for the venue  
The run ends with what changed, the exact message and the number of ticket holders it reached, ready to forward to the venue manager and the door team.

### What you get back

Example data

```
Club Night, 14 Nov, The Warehouse.
Changed: start 22:00 to 20:00. End 04:00 unchanged. Read back and matched.
Message sent with MIO Connect after your OK to 182 ticket holders: "Doors now open at 20:00. Your ticket is still valid."
Cut from your draft: "Grab early bird for our NYE party" (MIO Connect is for event information only).
Date unchanged, so DICE sends no reschedule email.
```

### Other ways to ask

- Kest cancelled. Take Kest off the Club Night line-up and tell ticket holders the rest of the night is unchanged.
- Rain: Rooftop Session moves to the indoor room at Skyline Terrace. Update the venue and message everyone with a ticket before 16:00.
- Last entry for Club Night is now 01:00\. Message ticket holders only, no event edit.

Before you automate it

## What DICE allows, and what to know first

- DICE's MIO user guidelines limit MIO Connect to operational messages about the event the fan is attending, and forbid discounts, vouchers, other events, surveys and requests to update marketing preferences.
- When a DICE event is officially rescheduled, the fan's ticket stays valid for the new date, DICE emails all ticket holders, and fans who cannot attend can request a refund.
- Under DICE's terms the promoter pays the refunds due after a cancellation or reschedule; DICE sets them off against sales proceeds or asks for the money within 48 hours.
- When a DICE event is cancelled, fans are refunded automatically to the original card once the organiser returns the ticket proceeds, and that refund cannot be reversed.
- DICE's terms make the promoter reimburse any costs DICE incurs in advertising or notifying fans of changes to an event.

update\_event and message\_attendees ask for your OK by default. To run it on a schedule without you, switch confirmation off for those tools in your dashboard.

Sources: [Make It On DICE: User Guidelines](https://support.dice.fm/article/761-mio-user-guidelines-english-language) · [DICE Self Sign-Up Terms and Conditions USA](https://support.dice.fm/article/764-mio-ticketing-terms-and-conditions-us) · [DICE Help: What to do if an event is cancelled, postponed or rescheduled](https://dicefm.zendesk.com/hc/en-gb/articles/19620455490193-What-to-do-if-an-event-is-cancelled-postponed-or-rescheduled) · [DICE Help: When are you entitled to a refund?](https://dicefm.zendesk.com/hc/en-gb/articles/4409603669777-When-are-you-entitled-to-a-refund)

REST

## Call message\_attendees from a script

curl

```
curl https://cotlet.dev/api/v1/dice/message_attendees \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"event_id":"ev_48213","message":"Doors now open at 20:00. Your ticket is still valid."}'
```

Example response

```
{
"event_id": "ev_48213",
"status": "sent",
"recipients": 182,
"sent_at": "2026-11-14T12:00:00+00:00"
}
```

MCP: add https://cotlet.dev/mcp/v1 with the same key; the tool is dice\_message\_attendees. Example data.

[Schedule it in n8n, Make, Zapier or cron](https://cotlet.dev/integrations/dice-api-mcp-server#automations)

Tools

## DICE tools this automation uses

__Cotlet DICE tools used to update a DICE event and message ticket holders__
| Tool | Parameters |
| ------------------ | ------------------ |
| get\_event | event\_id |
| update\_event | event\_id, fields |
| message\_attendees | event\_id, message |

[All 15 DICE tools with descriptions](https://cotlet.dev/integrations/dice-api-mcp-server#tools)

## Frequently asked questions

### Can I email fans from the All Customer Data download instead?

Only with the same kind of message. DICE's MIO user guidelines allow the All Customer Data download to be used for transactional or operational information about the event the fan bought a ticket for, and only fans in the Marketing Opt-ins download may receive marketing.

## More DICE automations

- [Get a weekly DICE ticket sales report with returns and transfers](https://cotlet.dev/integrations/dice-api-mcp-server/weekly-ticket-sales-report)
- [Create a DICE event draft with ticket types](https://cotlet.dev/integrations/dice-api-mcp-server/create-event-draft)
- [Add a new DICE ticket release when early bird sells out](https://cotlet.dev/integrations/dice-api-mcp-server/add-ticket-release)
- [DICE API and MCP server: every tool](https://cotlet.dev/integrations/dice-api-mcp-server)
- [All use cases](https://cotlet.dev/use-cases)

## Give your agent access to DICE.

Free 7-day trial with 5,000 credits, no card needed. Cotlet is independent and not affiliated with DICE.

[Request access](https://cotlet.dev/app/signup?app=dice)