Dice has no public API. How does Integuru access event and ticket data?

Integuru reverse-engineers the internal HTTP endpoints that Dice's web app uses and replays them directly. Your code calls Integuru's API; Integuru handles session management with Dice's backend without opening a browser, so requests complete reliably under 3 seconds.

How do I get events for a city I don't have a slug for?

Call search_cities first with a partial or full city name. The action returns matching city slugs that you can then pass to list_events. The search is case-insensitive and returns 10 results by default, which you can increase with the limit parameter.

I have an event URL from Dice. Can I pass that directly to get_event_tickets?

Yes. Pass the event URL slug (perm_name from the URL) as event_slug to get_event_tickets. If you don't have the 24-character event_id, the integration looks it up automatically before fetching ticket data.

Back to Integrations

Events & Ticketing

Dice

Integuru generates a production-ready HTTP API for Dice, the live events and ticketing platform. The integration covers 3 actions for event discovery, city lookup, and ticket retrieval, letting teams query Dice event data across cities programmatically without browser automation.

3actions

https://dice.fm/browse/new_york-5bbf4db0f06331478e9b2c59

Last reviewed: July 2026

Overview

Integuru's Dice integration provides production-ready HTTP API access to Dice, the live music and events ticketing platform at dice.fm, covering 3 actions including list_events and get_event_tickets. The integration lets you query events by city, look up city slugs, and retrieve ticket details for specific events.

No public API. Dice does not offer a developer API. Teams that need event data across cities previously had to scrape individual city pages manually, with no reliable way to enumerate tickets or check availability programmatically.

Teams building event discovery tools, music industry analytics platforms, or ticketing aggregators use this integration to pull Dice event data programmatically across multiple cities. The 3 actions cover the full lookup flow:

list_events: Returns up to 30 events for a given city slug.
search_cities: Resolves a city name to the slug that list_events requires.
get_event_tickets: Returns ticket availability and details for a specific event.

For other events and ticketing platforms, see CrowdVolt or EDM Train, or browse the full integrations catalogue.

Use Cases

Integuru's Dice integration covers the end-to-end flow from city discovery through event listing to individual ticket retrieval.

Event listing by city: Call list_events with a city_slug to retrieve up to 30 events for that city. The action defaults to New York (new_york-5bbf4db0f06331478e9b2c59) if you omit the slug.
City slug lookup: Use search_cities with a partial or full city name to find the correct city_slug for list_events. The search is case-insensitive and returns 10 results by default.
Ticket retrieval: Call get_event_tickets with either an event_id (the 24-character ID from event data) or an event_slug (the URL perm_name) to retrieve ticket availability and details for a specific event.

Setup Notes

Integuru's Dice integration authenticates against https://dice.fm/browse/new_york-5bbf4db0f06331478e9b2c59. Integuru handles session management automatically.

The list_events action has a maximum of 30 events per page. To retrieve events across multiple cities, call list_events once per target city_slug. Use search_cities first if you do not already have the slug for a city.

For get_event_tickets, you can supply either event_id or event_slug. If you provide only event_slug, the integration performs a lookup to resolve the corresponding event ID before fetching tickets. Providing event_id directly is faster if you already have it from a prior list_events call.

Available Actions

Click an action to expand its parameters

Overview

Use Cases

Setup Notes

Available Actions

Frequently Asked Questions