# DICE Events Scraper — Concert, Venue & Ticket Data (`aitorsm/dice-events`) Actor

Collect events from DICE (dice.fm): title, date, lineup, venue, and ticket details. In venue mode each show carries a full venue lead — Instagram, website, email, phone, and capacity. Built for booking, venue lead generation, and live-music market intelligence.

- **URL**: https://apify.com/aitorsm/dice-events.md
- **Developed by:** [Aitor Sanchez-Mansilla](https://apify.com/aitorsm) (community)
- **Categories:** Automation, Lead generation, E-commerce
- **Features:** Limited permissions
- **Stats:** 5 total users, 4 monthly users, 100.0% runs succeeded, 1 bookmarks
- **User rating**: No ratings yet

## Pricing

from $20.00 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## DICE Events Scraper — Promoters, Venues, Lineups, and Pricing for Music + Nightlife Lead Generation

[![DICE Events Scraper status](https://apify.com/actor-badge?actor=aitorsm/dice-events)](https://apify.com/aitorsm/dice-events)

Get structured **venue data** and **concert data** for live music events across 69+ cities from [DICE](https://dice.fm) — the mobile-first ticketing platform for live music, clubs, festivals, comedy, and cultural events. This Actor turns DICE listings into clean records covering events, the venues that host them, the promoters running them, and ticket pricing. Each event returns:

- Event name, description, start time, attendance type, sale status, and DICE event URL
- **Promoter (organizer) info** — billing promoter ID, name, and slug, plus additional marketeers
- **Full venue data** — name, full address, latitude/longitude, city, country
- **Lineup** — headliner act + supporting acts
- **Ticket pricing** — amount (minor units), currency, formatted display
- **Status signals** — `isTicketAvailable`, sold-out flag, waiting-list flag, `isTicketAvailableAtDoor`
- **Categorization** — primary tag (Gigs / DJ / Party / Festival / Comedy / Theatre / Film / etc.) plus secondary tag types
- Event flyer image URL and DICE social/share links

The Actor works for any of DICE's 69 catalog cities, wherever you run it from.

### Use Cases

#### 1. **Music Promoter Lead Generation**

DICE is where indie promoters, club nights, and festival operators sell tickets to live audiences. Every event exposes its `billingPromoter` (the org running the show) plus any additional `marketeers` (co-promoters / agencies). Pull a city's active promoter list with run-rate signals in one pass — ideal input for ticketing-platform BD, music-tech vendors, or sponsorship outreach.

#### 2. **Venue Data + Lead Generation + Booking Intel**

Each event carries the full venue record (name, address, lat/lng) — a clean source of **venue data** for any covered city. Run the `sweepVenues: true` mode to enumerate every DICE-listed venue in a city, and keep `enrichVenues: true` to turn each venue into a self-contained **lead row** — the venue's website, Instagram, Facebook, TikTok, Twitter/X, phone, email, capacity, and description, attached to every one of that venue's events. Ideal for booking agents identifying which rooms are actively programming, AV / production vendors mapping their addressable market, or anyone selling into venue operators directly.

#### 3. **Cross-Platform Organizer Database**

Combine DICE output with Eventbrite, Luma, Posh, and Meetup datasets for unified cross-platform organizer intelligence. DICE skews music + nightlife; the other platforms cover broader event categories. Together they form a complete picture of who's running paid events in a city.

#### 4. **Concert Data + Festival Market Intelligence**

Build a **concert data** feed for live music events: track which acts are touring, which venues are programming them, and at what price points. The `summaryLineup` (headliner) + `lineupSupports` fields give act-level granularity; `priceAmount` + `priceCurrency` lets you compare ticket-price trends across cities or sub-genres.

#### 5. **Talent and Booking Pipeline**

For booking agencies, A\&R teams, or content platforms: surface emerging acts being booked at indie venues before they show up on the big-room tour cycle.

#### 6. **Event Aggregation for Local Apps and Newsletters**

Pull a clean structured feed of upcoming music + nightlife events in a city for use in "what's on tonight" newsletters, tourism sites, hotel concierge apps, or co-working community boards.

#### 7. **Ad-Targeting and Audience Research**

Use venue addresses + event categories to inform geo-targeted ads (Meta / TikTok) at audiences with confirmed music-event affinity. Multi-platform overlap (DICE event in same building as Posh event) is a strong "active scene" indicator.

#### 8. **Competitive Tracking for Ticketing Platforms**

If you sell ticketing infrastructure, the list of promoters currently using DICE is your would-be customer list. Run weekly and diff to spot churn or growth.

> **On the roadmap**: deeper per-venue event coverage, Apple Music / Spotify track preview links, and full per-event detail enrichment. [Drop me a line](mailto:business@aitorsm.com) if any of these would unblock a use case — it helps me prioritize.

### Cost

This Actor uses **pay-per-event** pricing:

- **$0.03 per event**
- **$0.02 per unique venue enriched** — only charged when `enrichVenues` is on (the default) and only in venue-sweep mode, and only once per venue per run (deduplicated across all of that venue's events). Turn `enrichVenues` off to pay for events alone.

Apify's platform costs are included, so the total is predictable. A typical venue sweep that surfaces 60 venues with enrichment on costs roughly the per-event total plus ~$1.20 (venues) for **60 venue lead rows** carrying website, socials, phone, and email.

### Input

The actor takes a single city per run, with three escalating sweep modes for coverage depth.

- **`city`** — name of any of DICE's 69 supported cities (e.g. `"Los Angeles"`, `"London"`, `"Barcelona"`, `"Berlin"`, `"New York"`, `"Tokyo"`). Matching is fuzzy and case-insensitive.
- **`cityPermName`** / **`cityId`** *(advanced)* — DICE's own identifiers for a city. Pass both together to target a city directly and skip name resolution. Useful if you've already resolved the city.
- **`maxItems`** — global cap on events returned (deduped across all sweep paths). Leave at the default `30` for a quick preview, or raise to thousands for a full sweep.
- **`sweepFilters`** *(boolean, default `false`)* — when true, the actor covers the city across all primary categories (Gigs / DJ / Party / Comedy / Theatre / Film / Workshop / Talk / Wellbeing / Playback / Artist signing / etc.). Yields **~3-4× more events** than the default view. Best for organizer/promoter discovery.
- **`sweepVenues`** *(boolean, default `false`)* — when true, the actor covers **every DICE venue in the city** and returns each venue's full event list. Yields the most exhaustive coverage (~10× the default), scaling with the city's venue count (e.g. 84 for LA, 163 for Barcelona). Best for event-listing use cases or maximum-coverage lead-gen. Composes with `sweepFilters` — all events deduped by ID.
- **`enrichVenues`** *(boolean, default `true`)* — when on (in `sweepVenues` mode), each venue contributes its contact + social block — `venueWebsite`, `venueInstagram`, `venueFacebook`, `venueTiktok`, `venueTwitter`, `venuePhone`, `venueEmail` — plus `venueCapacity`, `venueDescription`, and the venue's address. These fields are attached to every one of that venue's events. **Recommended for venue lead-generation** — it's what turns a venue listing into a contactable lead. Billed once per unique venue ($0.02, deduplicated). Has no effect unless `sweepVenues` is also on; turn it off to omit the contact/social fields and pay for events alone.

**Run status:** an unknown city finishes `SUCCEEDED` with 0 rows. If the city list or every event page cannot be retrieved, the run **fails** with a clear error message instead of returning an empty dataset.

#### Sample inputs

**Quick city preview** (~30 events):

```json
{ "city": "Los Angeles", "maxItems": 30 }
```

**Promoter lead-gen sweep** (~130 events, ~40 promoters):

```json
{ "city": "Los Angeles", "maxItems": 1000, "sweepFilters": true }
```

**Venue lead-gen sweep** (every LA venue with website + socials + phone + email):

```json
{ "city": "Los Angeles", "maxItems": 10000, "sweepVenues": true, "enrichVenues": true }
```

**Maximum-coverage sweep** (~420 events, ~55 promoters for LA):

```json
{ "city": "Los Angeles", "maxItems": 10000, "sweepFilters": true, "sweepVenues": true }
```

### Output

The data is returned in **JSON format**, ideal for direct ingestion into analytics platforms, CRMs, dashboards, or downstream pipelines.

#### Example entry

Input: `{ "city": "Barcelona", "maxItems": 1 }`

```json
{
  "eventId": "6a06e30b1d609200016c1160",
  "permName": "mx9oqr-churros-con-chocolate-antichurros-special-pride-night-sbado-18th-jul-sala-apolo-barcelona-tickets",
  "url": "https://dice.fm/event/6a06e30b1d609200016c1160-mx9oqr-churros-con-chocolate-antichurros-special-pride-night-sbado-18th-jul-sala-apolo-barcelona-tickets",
  "name": "CHURROS CON CHOCOLATE / ANTICHURROS - Special Pride Night (sábado)",
  "about": {
    "description": "¡No te pierdas nuestro especial PRIDE del sábado! En nuestra segunda noche de celebración del Orgullo contaremos con la fórmula CHURROS CON CHOCOLATE + ANTI...",
    "highlights": [
      { "type": "age_restriction", "title": "Para mayores de 18 años (necesario traer DNI)." }
    ]
  },
  "startUnix": 1784411940,
  "startIso": "2026-07-18T21:59:00.000Z",
  "attendanceType": "live_only",
  "status": "sold-out",
  "secondaryStatus": "waiting-list",
  "isTicketAvailable": true,
  "isTicketAvailableAtDoor": false,
  "hasMultipleTicketTypes": false,
  "priceAmount": 2425,
  "priceCurrency": "EUR",
  "priceDisplay": null,
  "billingPromoterId": "4679",
  "billingPromoterName": "CHURROS CON CHOCOLATE",
  "billingPromoterPermName": "churros-con-chocolate-7289",
  "marketeers": [
    { "id": 525, "name": "Sala Apolo" },
    { "id": 843, "name": "PUMALU2 (CHURROS CON CHOCOLATE)" }
  ],
  "summaryLineup": null,
  "lineupSupports": [],
  "eventTag": null,
  "tagsTypes": [
    { "name": "party", "value": "music:party", "title": "Party" }
  ],
  "venueId": "3008",
  "venueName": "SALA APOLO",
  "venueCity": "Barcelona",
  "venueCityId": "5d8cefe1e3e6e374e99e8cbe",
  "venueCountry": "Spain",
  "venueAddress": "Carrer Nou de la Rambla, 113, 08004 Barcelona, Spain",
  "venueLat": 41.3743117,
  "venueLon": 2.1695412999999917,
  "socialLinks": {
    "event_share": "https://link.dice.fm/Z27cee70269b?dice_id=Z27cee70269b"
  },
  "imageUrl": "https://dice-media.imgix.net/attachments/2026-05-15/dd0b4aa2-2f7f-4ca4-a4c2-523bd8c4e844.jpg?rect=0%2C432%2C2160%2C1296",
  "scrapedFromCity": "Barcelona, Spain",
  "scrapedFromCityPermName": "barcelona",
  "scrapedFromCityId": "5d8cefe1e3e6e374e99e8cbe",
  "scrapedCityNameFromPage": "Barcelona",
  "scrapedAt": "2026-05-22T21:48:40.184Z"
}
```

#### Fields

| Field | Purpose |
|---|---|
| `eventId`, `permName`, `url` | DICE event identifiers + canonical URL |
| `name`, `about` | Event title + full description (with highlights) |
| `startUnix`, `startIso` | Event start time (epoch + ISO 8601 UTC) |
| `attendanceType`, `status`, `secondaryStatus` | `live_only` / `streaming` / etc.; `live` / `sold-out` / `cancelled`; `waiting-list` etc. |
| `isTicketAvailable`, `isTicketAvailableAtDoor`, `hasMultipleTicketTypes` | Availability signals at collection time |
| `priceAmount`, `priceCurrency`, `priceDisplay` | Ticket price (minor units), ISO currency code, formatted display string |
| `billingPromoterId`, `billingPromoterName`, `billingPromoterPermName` | The organizer running the event |
| `marketeers[]` | Additional co-promoters / agencies |
| `summaryLineup`, `lineupSupports[]` | Headliner act + supporting acts |
| `eventTag`, `tagsTypes[]` | Primary tag (Gigs/DJ/Party/etc.) + secondary classification |
| `venueId`, `venueName`, `venueAddress`, `venueLat`, `venueLon`, `venueCity`, `venueCountry` | Full venue record with geo coordinates |
| **`venueLinks`** | Venue's social block `{facebook, instagram, tiktok, twitter, website}` — present when `enrichVenues=true` (venue-sweep mode) |
| **`venueWebsite`, `venueInstagram`, `venueFacebook`, `venueTiktok`, `venueTwitter`** | Flat per-platform venue links — present when `enrichVenues=true` |
| **`venuePhone`, `venueEmail`** | Venue contact details — present when `enrichVenues=true`. The direct-contact lead payload |
| **`venueCapacity`, `venueDescription`, `venueProfileAddress`** | Venue capacity, description, and profile address — present when `enrichVenues=true` |
| `socialLinks` | DICE-hosted share + referral links |
| `imageUrl` | Event flyer (landscape preferred, square / portrait fallback) |
| `scrapedFromCity`, `scrapedFromCityPermName`, `scrapedFromCityId`, `scrapedCityNameFromPage`, `scrapedAt` | Run metadata (requested city display name, slug, ID; city name as shown by DICE; collection timestamp) |

#### Simplified Overview

A simplified view of this data is shown directly in the **Apify console**, where you can see a table of key event details: event name, flyer, start date, venue, city, promoter, ticket price, and availability.

```json
{
  "name": "CHURROS CON CHOCOLATE / ANTICHURROS - Special Pride Night",
  "imageUrl": "https://dice-media.imgix.net/attachments/.../flyer.jpg",
  "startIso": "2026-07-18T21:59:00.000Z",
  "venueName": "SALA APOLO",
  "venueCity": "Barcelona",
  "billingPromoterName": "CHURROS CON CHOCOLATE",
  "priceDisplay": "24,25 €",
  "isTicketAvailable": true,
  "url": "https://dice.fm/event/..."
}
```

***

### How to Use

1. **Pick a city** — type any of DICE's 69 supported city names (e.g. `"Los Angeles"`, `"Berlin"`, `"Tokyo"`).
2. **Choose your sweep mode**:
   - Default → quick preview (~30 events)
   - `sweepFilters: true` → broad category sweep (~130 events)
   - `sweepFilters + sweepVenues` → maximum coverage (~400+ events)
3. **Set `maxItems`** to cap the total budget.
4. **Run the Actor** — check the Overview tab to see events as they arrive.
5. **Export the dataset** — JSON, CSV, Excel, or HTML. Drop into your CRM, spreadsheet, dashboard, or downstream enrichment pipeline.

***

Start collecting DICE events today by running this Actor on Apify.

### FAQ

**What venue data does this return?**
In venue-sweep mode with enrichment on, each venue comes back with its name, full address, latitude/longitude, capacity, description, website, Instagram, Facebook, TikTok, Twitter/X, phone, and email — a complete **venue data** row attached to every one of that venue's events. That makes it a direct source for venue lead lists and booking intelligence.

**What concert data is available?**
Every event includes its name, description, start time, category (Gigs / DJ / Party / Festival / Comedy, etc.), headliner and supporting acts, ticket price + currency, and live availability signals (on sale, sold out, waiting list, at-the-door). Together that gives you structured **concert data** for live music events across a city.

**Which cities are covered?**
Any of DICE's 69 catalog cities worldwide — including Los Angeles, London, Barcelona, Berlin, New York, and Tokyo. City targeting is URL-based, so the Actor works for any catalog city regardless of where the run originates.

**How do I get the most coverage for a city?**
Combine the sweep modes: `sweepFilters: true` covers all event categories (~3-4× the default view), and `sweepVenues: true` enumerates every venue in the city and returns each venue's full event list (~10× the default). They compose, and all events are deduplicated by ID.

**Can I run it on a schedule to track changes?**
Yes. Schedule the Actor weekly per city and diff the output to spot new venues, new promoters, price movements, and which rooms are actively programming. It also runs through Apify's integrations for downstream pipelines.

**Do I need a DICE account or API key?**
No. This Actor returns the full structured record per event and venue — lineups, prices, availability signals, and complete venue contact rows — with no account, key, or quota to manage: point it at a catalog city and export.

### Related Actors

Building an event-data set across platforms? These pair naturally with this Actor:

- [Resident Advisor Events](https://apify.com/aitorsm/ra-events) — electronic music events plus enriched promoter data.
- [Eventbrite Events](https://apify.com/aitorsm/eventbrite) — broad ticketed-event coverage + organizer contact data.
- [Luma Events](https://apify.com/aitorsm/luma-events) — tech, community, and founder events with organizer socials.
- [Posh Events](https://apify.com/aitorsm/posh-events) — US nightlife events and the promoters behind them.
- [Email & Contact Extractor](https://apify.com/aitorsm/email-extractor) — turn any list of venue or promoter websites into emails and phone numbers.

**Related reading:** [The contact-enrichment cascade — what order to fire your tools in](https://www.linkedin.com/pulse/contact-enrichment-cascade-what-order-fire-your-tools-aitor-165ae/) — how to turn the venue / promoter websites this Actor surfaces into emails and phones, cheapest-first (with real hit rates per step).

### Contact

- **Email**: <business@aitorsm.com> — for custom features, advanced filtering, tailored data products, or anything off-spec.
- **Apify Discord**: find me as `aitor.sm`.

If this actor has been useful to you, please consider adding it to your bookmarks 📑 on Apify.

# Actor input Schema

## `city` (type: `string`):

Pick a city from the list, or type any DICE city yourself (name is matched against DICE’s live city list, so newly-added cities work too). For an unlisted city you can also pass cityPermName + cityId in the advanced section.

## `country` (type: `string`):

Country of the city, e.g. "United Kingdom". Disambiguates repeated city names — DICE lists both London, Canada and London, United Kingdom under the same perm_name, and without this the Canadian one wins. Leave empty to accept the first match.

## `cityPermName` (type: `string`):

DICE city permanent slug (e.g. "LosAngeles", "london"). Required when also passing `cityId`. Overrides `city`.

## `cityId` (type: `string`):

DICE city ObjectId hex (24 chars). Required when also passing `cityPermName`.

## `maxItems` (type: `integer`):

Maximum number of events to return. Without sweepFilters, the default city view lists up to ~30 events. With sweepFilters=true, up to ~400 per city.

## `sweepFilters` (type: `boolean`):

If true, the actor also covers each primary category (Gigs/DJ/Party/Sport/Comedy/Theatre/Workshop/Art/Social/Film/Talk/Wellbeing/Playback/Artist signing). Yields ~3-4x more events per city than the default 30 and takes slightly longer. Best for organizer/promoter discovery.

## `sweepVenues` (type: `boolean`):

If true, covers every DICE venue in the city and returns each venue's full event list. Yields the most exhaustive coverage (~3x more events than filter sweep); run time scales with the city's venue count (e.g. 84 for LA). Best for event-listing use cases. Composes with sweepFilters — all events deduped by ID.

## `enrichVenues` (type: `boolean`):

If true, each venue visited in sweepVenues mode is enriched with its contact + social details (website, Instagram, Facebook, TikTok, Twitter/X, phone, email) plus capacity, description, and address. Billed once per unique venue ($0.02). Recommended for venue lead-generation. Has no effect unless sweepVenues is also on.

## Actor input object example

```json
{
  "city": "Los Angeles",
  "country": "United Kingdom",
  "maxItems": 30,
  "sweepFilters": false,
  "sweepVenues": false,
  "enrichVenues": true
}
```

# Actor output Schema

## `overview` (type: `string`):

No description

## `venues` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "city": "Los Angeles",
    "maxItems": 30
};

// Run the Actor and wait for it to finish
const run = await client.actor("aitorsm/dice-events").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "city": "Los Angeles",
    "maxItems": 30,
}

# Run the Actor and wait for it to finish
run = client.actor("aitorsm/dice-events").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "city": "Los Angeles",
  "maxItems": 30
}' |
apify call aitorsm/dice-events --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,aitorsm/dice-events"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/kVmnBOvyDGAzueMeP/builds/tSMB1DMdBHBoVxqAQ/openapi.json