# DICE Events Scraper — every gig, club night and show in a city (`northbell/dice-events-scraper`) Actor

Every event DICE lists in a city for the dates you pick: name, start time, venue and address, type, price, sold-out status, ticket sale dates and image. Gets past the 24-event limit, and returns only new, sold-out or re-priced events since the last run. No login.

- **URL**: https://apify.com/northbell/dice-events-scraper.md
- **Developed by:** [Northbell](https://apify.com/northbell) (community)
- **Categories:** Lead generation, Marketing
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.60 / 1,000 events

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 — every gig, club night and comedy show in a city

Read every event **DICE (dice.fm)** lists in a city for the days you pick: **name, start time, venue and address, event type (gig, DJ, party, comedy, theatre …), price, sold-out status, ticket sale dates and the picture**. One clean row per event, for London, New York, Paris, Berlin, Barcelona, Madrid, Milan, Los Angeles, Manchester and every other DICE city. **$2.00 per 1,000 events**, no login, no API key.

**Not cut off at 24.** DICE shows 24 events at a time and the rest only to its own app. This Actor reads each day, then each event type, then narrower price bands and genres, until every window fits, so a Saturday in London comes back with all of its 160+ events, not the first 24.

Fixed 22 Oct 2026: when the previous run stopped before the end of its days (at *maxEventsPerCity*, your charge limit or the time limit), events on the days it had not reached counted as new, so with *returnOnly: new* a second run could return existing events as new and charge for them. Now an unseen event on a day the previous run did not finish is new only if DICE announced it after that run; unseen events on days it did read are still new.

**Built for watching a city.** Pick *New events and events that sold out or changed price* and every run returns only what changed since your previous run: newly announced shows, shows that just sold out, and price changes.

### What you get

| Field | What it is |
|---|---|
| `name`, `url`, `eventId` | the event, its page on DICE and its DICE id |
| `startsAt`, `endsAt`, `localStart`, `timezone`, `isMultiDay` | start and end (UTC), the start in the city's own time, the time zone, and whether it runs over several days |
| `category` | the DICE event type: `music/gig`, `music/dj`, `music/party`, `culture/comedy`, `culture/theatre`, `culture/film` … |
| `venue`, `venueAddress`, `venueId`, `otherVenues`, `city`, `country`, `countryCode` | where it is |
| `price`, `priceFrom`, `currency`, `isFree` | the ticket price, or the "from" price when there are several tiers, and the currency (GBP, USD, EUR …) |
| `status`, `isSoldOut` | the ticket status DICE shows (`on-sale`, `sold-out` …) |
| `announcedAt`, `saleStartsAt`, `saleEndsAt` | when the event was announced and when tickets go on and come off sale |
| `summary`, `tag`, `ticketType`, `imageUrl` | the one-line description, DICE's tag, how tickets are taken (`purchase` …) and the square picture |
| `isNewSinceLastRun`, `firstSeenAt`, `previousStatus`, `statusChanged`, `previousPrice`, `priceChanged` | the change since your previous run of the same city and types: empty on the first run |
| `observedAt` | when this row was read |

Each city also gets one free `summary` row: `eventsRead`, `eventsReturned`, `newSinceLastRun`, `changedSinceLastRun`, `filteredOut` (sold out, when you leave those out), `pagesFetched`, the days read, `stoppedBecause` (`end-of-range`, `limit`, `time-limit` or `error`) and `incompleteWindows` (see Notes). A city that cannot be read gives a free `error` row.

Shape of a row (shortened):

```json
{
  "type": "event", "eventId": "6abe416d7fbb6f0001bf6ce6", "url": "https://dice.fm/event/6abe416d7fbb6f0001bf6ce6",
  "name": "A:M After Hours", "category": "music/party", "status": "on-sale", "isSoldOut": false,
  "startsAt": "2026-10-24T02:00:00.000Z", "endsAt": "2026-10-24T09:00:00.000Z", "localStart": "2026-10-24T03:00:00+01:00", "timezone": "Europe/London",
  "venue": "Lightbox", "venueAddress": "6A S Lambeth Pl, London SW8 1SP", "city": "London", "countryCode": "GB",
  "price": null, "priceFrom": 0, "currency": "GBP", "isFree": false,
  "saleStartsAt": "2026-09-30T23:15:00.000Z", "saleEndsAt": "2026-10-24T06:00:00.000Z",
  "isNewSinceLastRun": true, "statusChanged": false, "priceChanged": false,
  "observedAt": "2026-10-19T04:26:03.425Z"
}
```

### Run it again and again

- **On a schedule** — save your input as a task and add a **Schedule**: every hour or every morning. Send each run to Slack, Discord, Telegram, Google Sheets or email with an integration on the task.
- **Watch for changes** — Set **Return** to *New events and events that sold out or changed price*.
- **In bulk** — Put every city you follow in **Cities** and read up to 90 days in one run.

### Use it for

- **Event listings and city guides** — every gig, club night and comedy show in your city, with venue, time and price, for your site, app or newsletter
- **Promoters, venues and agents** — see what else is on the same night, what sells out and how others price their tickets
- **Artists' and labels' teams** — know as soon as a show is announced or sells out
- **Market research** — which types of events, venues and price levels each city has, week by week

### Input

```json
{
  "cities": ["London", "Manchester", "https://dice.fm/browse/paris-5b23e8a0e63cc224a4c36a2d/culture/comedy"],
  "categories": ["gig", "comedy"],
  "dateFrom": "2026-11-01",
  "days": 7,
  "maxEventsPerCity": 1000,
  "returnOnly": "new-or-changed",
  "includeSoldOut": true
}
```

- **cities** — city names as DICE uses them, or the address of a city page on dice.fm. An address that ends in an event type reads only that type.
- **categories** — optional: only these event types (`gig`, `dj`, `party`, `comedy`, `theatre`, `film` …, or `music` / `culture` for a whole group).
- **dateFrom**, **days** — the first day (default today, in each city's own time) and how many days, up to 90.
- **maxEventsPerCity** — stop a city after this many events (default 1,000).
- **returnOnly** — `all`, `new`, or `new-or-changed`.
- **includeSoldOut** — leave out sold-out events when switched off.

The memory behind *since the last run* is kept per city and per choice of types in a named key-value store in your Apify account, so the second run already shows what changed. It does not depend on the days you pick: an event read last week and again today is not new.

### Pricing

**$2.00 per 1,000 events** ($0.002 each), plus $0.001 per run. Summary rows and error rows are free. With *new* or *new-or-changed* you pay only for the events returned, so an hourly check of a city that finds 5 changes costs about $0.011.

### Notes

- **Public data only**: what anyone sees on dice.fm without signing in. The Actor does not buy, hold or check tickets.
- **Speed**: about 1.5 pages a second, all from dice.fm one after the other. A day in London takes 10 to 40 seconds (more on Fridays and Saturdays, when the busiest types are split by price and genre); a quiet city takes a few seconds.
- **Completeness**: when even a single genre in a 1-unit price band on one day has more than 24 events, a few events in it can be missing. Such windows are listed in the city's `incompleteWindows`, so you know where; on the busiest Saturday we tried in London there were none.
- **Days**: an event that starts after midnight is read on its own day. Multi-day events are returned once.
- **Event types** come from DICE. An event belongs to one type. A type that has no events on a day is skipped.
- **Prices** are in the city's currency, in whole units (12.5 = £12.50). `price` is the ticket price; when DICE shows "from" a price (several tiers), it is in `priceFrom` and `price` is empty.
- If DICE refuses the requests the city gets an error row; busy responses (429) and connection errors are retried twice. The Actor does not get around bot checks.

### For AI agents

`{"cities": ["London"], "categories": ["comedy"], "days": 3}` returns every comedy event in London for the next three days, one row per event, plus one summary row. Rows have `type`: `event`, `summary` or `error`. To watch over time, call it again with the same cities and types and `"returnOnly": "new-or-changed"`: every event row returned is new, sold out or re-priced since the previous call.

# Actor input Schema

## `cities` (type: `array`):

One per line: a city name as DICE uses it (London, New York, Paris, Berlin, Barcelona, Madrid, Milan, Los Angeles, Manchester …) or the address of a city page on dice.fm (https://dice.fm/browse/london-54d8a23438fe5d27d500001c). An address that ends in an event type (…/music/gig) reads only that type. If a name is not found, open dice.fm, pick the city and paste the address of its page.

## `categories` (type: `array`):

Leave empty for every type. One per line, as DICE names them: gig, dj, party, comedy, theatre, social, film, sport, talks, workshop, art, foodanddrink, wellbeing, podcast, or the path (music/gig, culture/comedy). "music" or "culture" alone takes every type in that group.

## `dateFrom` (type: `string`):

The first day to read, as YYYY-MM-DD. Leave empty to start today (in each city's own time).

## `days` (type: `integer`):

How many days to read from the first day, up to 90. A busy city such as London has 70 to 170 events a day.

## `maxEventsPerCity` (type: `integer`):

Stop a city after this many events, up to 20,000. Events are read day by day, so the earliest days come first.

## `returnOnly` (type: `string`):

all = every event read. new = only events you have not seen in an earlier run of the same city and types. new-or-changed = new events plus events whose ticket status (for example sold out) or price changed. The first run has nothing to compare with and returns everything it read.

## `includeSoldOut` (type: `boolean`):

Switch off to leave out events that are sold out. With "new-or-changed", an event that has just sold out is still returned so you see the change.

## Actor input object example

```json
{
  "cities": [
    "London"
  ],
  "days": 7,
  "maxEventsPerCity": 1000,
  "returnOnly": "all",
  "includeSoldOut": true
}
```

# Actor output Schema

## `events` (type: `string`):

Name, start time, venue, type, price, sold-out status and the link to each event.

## `cities` (type: `string`):

One row per city: how many events were read, returned, new and changed since the last run.

# 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 = {
    "cities": [
        "London"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("northbell/dice-events-scraper").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 = { "cities": ["London"] }

# Run the Actor and wait for it to finish
run = client.actor("northbell/dice-events-scraper").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 '{
  "cities": [
    "London"
  ]
}' |
apify call northbell/dice-events-scraper --silent --output-dataset

```

## MCP server setup

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

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/HgaP92dsP7amVTIEe/builds/NR6Az29ouMZ9drABE/openapi.json