# Dice.fm Scraper — Events & Ticket Status (`crawloop/dice-fm-scraper`) Actor

Scrape Dice.fm events by city, venue, artist, or promoter URL. Dates, venues, GPS, lowest ticket price, sold-out and waiting-list status from public pages. HTTP only, no login.

- **URL**: https://apify.com/crawloop/dice-fm-scraper.md
- **Developed by:** [Andrej Kiva](https://apify.com/crawloop) (community)
- **Categories:** Travel, Lead generation, Automation
- **Stats:** 3 total users, 2 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.00 / 1,000 event 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.fm Scraper — Events & Ticket Status

> **Disclaimer:** Unofficial tool — not affiliated with, sponsored by, or endorsed by DICE FM Ltd, Fever, or their affiliates. Data is read from publicly accessible pages only. No login. You are responsible for complying with applicable law (including GDPR where personal data appears) and the site’s terms. No warranty on accuracy or availability. Provided for informational and research use.

**Dice.fm scraper** for Apify — a **Dice.fm events scraper** for **city browse**, **venue / artist / promoter pages**, and **event URLs**. Built for **nightlife calendars**, **ticket-status monitors**, and **promoter research**. Export dates, venues, GPS, lowest ticket price, sold-out / waiting-list flags, and billing promoters as JSON. A practical **Dice.fm API alternative** for Python, Node.js, Sheets, and **MCP** / AI assistants. HTTP-only (no browser).

> **Crawloop Events suite** — Dice-exclusive gigs, ticketed nightlife, editorial club calendars, and general catalogs.

| Dice.fm Scraper ◄── you are here | [Shotgun Scraper](https://apify.com/crawloop/shotgun-scraper) | [Resident Advisor Scraper](https://apify.com/crawloop/resident-advisor-scraper) | [Eventbrite Scraper](https://apify.com/crawloop/eventbrite-scraper) |
| :--- | :--- | :--- | :--- |
| Dice-exclusive gigs, clubs, comedy, ticket status | Ticketed club nights, prices, SKUs | Club nights, RA clubs & DJs | Conferences, city search, organizers |

### When to use this Actor

- **Dice.fm city scraper** — London, Berlin, New York, or any city Dice lists
- **Dice.fm event scraper** — paste `/event/…` URLs for description, doors, age limit, and promoter
- **Venue / artist / promoter calendars** — upcoming shows on a public profile
- **Change monitor** — scheduled runs that emit only new or changed events (price, sold-out, waiting-list)
- **Dice.fm API alternative** — public-page dataset when you do not have a partner MIO token

### When not to use this Actor

- **Ticket SKUs, fees, or checkout holds** — listing pages expose lowest price and on-sale status, not every tier
- **Partner orders, ticket holders, or fan PII** — that GraphQL API is partner-gated
- **Unlimited “all events worldwide” dumps** — city browse returns first SSR pages per category (no HTML page 2)
- **Private or unlisted events** — public listings only
- **RA club lineups or Eventbrite conferences** — use the suite siblings linked above
- **Nightlife SKUs and checkout-style ticket types** — use [Shotgun Scraper](https://apify.com/crawloop/shotgun-scraper)

### Key features

- **HTTP-first** — city browse and event `__NEXT_DATA__`. No headless browser
- **Same public fields as the listing page** — id, title, dates, venue, GPS, lowest price, sold-out / waiting-list, promoter
- **Optional details pass** — description, age limit, doors-open, highlights
- **City names, not ObjectIds** — type `London`; UK London is preferred when names collide
- **Monitor mode** — remember events between runs; emit only `new` or `changed`
- **Caps that save budget** — `maxItems`, optional category shelf instead of a full city sweep
- **Proxy optional** — public catalog usually works from datacenter HTTP

### Input Parameters

| Parameter | Type | Default | Description |
| :--- | :--- | :--- | :--- |
| `locations` | Array | — | City names (`London`, `Berlin`, `New York`) or a browse token |
| `startUrls` | Array | — | Event, venue, artist, promoter, or `/browse/` URLs (auto-detected) |
| `category` | String | `all` | `gig`, `dj`, `party`, `comedy`, … or `all` for a city sweep |
| `dateFrom` / `dateTo` | String | — | Optional `YYYY-MM-DD` window on event start |
| `scrapeDetails` | Boolean | `false` | Extra event-page request (description, doors, age) |
| `maxItems` | Integer | `50` | Hard event cap (`0` = no cap, still first pages only) |
| `monitorMode` | Boolean | `false` | Emit only new & changed rows |
| `monitorKey` | String | `default` | Isolated monitor memory per saved search |
| `requestDelaySecs` | Number | `0.2` | Delay between HTTP requests |
| `proxyConfiguration` | Object | off | Enable only if you see 403/429 |

Provide **at least one** of: `locations`, `startUrls`.

#### Input example — city catalog

```json
{
  "locations": ["London"],
  "category": "gig",
  "maxItems": 50,
  "scrapeDetails": false
}
```

#### Input example — venue calendar

```json
{
  "startUrls": [
    {"url": "https://dice.fm/venue/fabric-vvpd"}
  ],
  "maxItems": 20
}
```

#### Input example — monitor a city

```json
{
  "locations": ["Berlin"],
  "category": "dj",
  "monitorMode": true,
  "monitorKey": "berlin-dj",
  "maxItems": 100
}
```

### Output

One dataset row per event.

| Field | Description |
| :--- | :--- |
| `id` / `permName` / `url` | Event id, slug, canonical page |
| `name` | Title |
| `startDate` / `endDate` / `timezone` | Start/end and IANA zone |
| `status` / `isSoldOut` / `isWaitingList` | On-sale, sold-out, waiting-list |
| `priceFrom` / `currency` / `isFree` | Lowest public price in major units |
| `venueName` / `venueAddress` / `city` / `country` | Venue + city |
| `latitude` / `longitude` | Venue GPS when the payload includes it |
| `promoterName` / `presentedBy` | Billing promoter |
| `lineup` / `tags` | Artist names and category tags when present |
| `description` / `ageLimit` / `doorsOpen` | Filled in details mode or on event URLs |
| `monitorChange` | `new` or `changed` when monitor mode is on |

#### Output example

```json
{
  "recordType": "event",
  "id": "6a96c6a465e90c0001b91585",
  "permName": "6dgpq8-horse-meat-disco-new-york-halloween-31st-oct-knockdown-center-new-york-tickets",
  "name": "Horse Meat Disco New York Halloween",
  "url": "https://dice.fm/event/6dgpq8-horse-meat-disco-new-york-halloween-31st-oct-knockdown-center-new-york-tickets",
  "status": "sold-out",
  "isSoldOut": true,
  "isWaitingList": true,
  "priceFrom": 119.48,
  "currency": "USD",
  "startDate": "2026-10-31T23:00:00-04:00",
  "venueName": "Knockdown Center",
  "city": "New York",
  "countryCode": "US"
}
```

### Use cases

- Build a city “what’s on” feed for gigs, DJ nights, and comedy
- Watch sold-out and waiting-list flips on a schedule
- Map ticket-price ranges across venues in one city
- Follow a promoter or venue calendar without a partner API key
- Chain nightlife inventory with Shotgun, Resident Advisor, or Eventbrite for the same city

### How to scrape Dice.fm with Python, Node.js, or cURL

Replace `YOUR_TOKEN` with an Apify API token. Actor name: `crawloop/dice-fm-scraper`.

#### Node.js

```javascript
import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('crawloop/dice-fm-scraper').call({
  locations: ['London'],
  category: 'gig',
  maxItems: 20,
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items.slice(0, 5));
```

#### Python

```python
from apify_client import ApifyClient

client = ApifyClient("YOUR_TOKEN")
run = client.actor("crawloop/dice-fm-scraper").call(run_input={
    "locations": ["London"],
    "category": "gig",
    "maxItems": 20,
})
items = client.dataset(run["defaultDatasetId"]).list_items().items
print(items[:5])
```

#### cURL

```bash
curl "https://api.apify.com/v2/acts/crawloop~dice-fm-scraper/runs?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"locations":["London"],"category":"gig","maxItems":20}'
```

### MCP and AI assistants

Use this Actor from AI tools via [Apify MCP](https://docs.apify.com/platform/integrations/mcp).
Connect your Apify account, then call this Actor by its Store ID `crawloop/dice-fm-scraper`.

Example prompts:

- "Run Dice.fm Scraper for locations London, category gig, max 30 events, and return name, date, venue, price, and URL as JSON"
- "Scrape Dice.fm DJ nights in Berlin and summarize sold-out vs on-sale counts"
- "Chain Dice.fm Scraper then Shotgun Scraper for London this weekend — Dice ticket status plus Shotgun SKUs"

### FAQ

**Does this use the official Dice API?**
No. The partner Ticket Holders API needs a MIO token. This Actor reads the same public browse and event pages a guest browser gets.

**Why do I only get the first page of a category?**
Dice browse HTML does not paginate with `?cursor=`. The Actor sweeps category first pages (and the popular shelf when `category` is `all`). Slice by city and category rather than one global dump.

**Are ticket tiers included?**
No. Rows include the lowest public price and on-sale / sold-out / waiting-list status. SKU lists are not on the public SSR payload.

**Do I need a proxy?**
Usually not. Turn on Apify Proxy only if browse returns 403/429.

**Does monitor mode charge for unchanged events?**
No. Unchanged rows are skipped and not written to the dataset.

**Can I scrape Dice.fm with Python or Node.js?**
Yes. Call `crawloop/dice-fm-scraper` from the Apify client (examples above) or via **MCP**. The dataset is JSON.

### What to run next

After a Dice.fm city dump, run [Shotgun Scraper](https://apify.com/crawloop/shotgun-scraper) for the same city when you need nightlife SKUs and display prices. Use [Resident Advisor Scraper](https://apify.com/crawloop/resident-advisor-scraper) for editorial club calendars and DJ lineups, and [Eventbrite Scraper](https://apify.com/crawloop/eventbrite-scraper) when the same weekend also has ticketed conferences.

### Related Actors

- [Shotgun Scraper](https://apify.com/crawloop/shotgun-scraper) — Shotgun.live events, venues, artists, ticket prices
- [Resident Advisor Scraper](https://apify.com/crawloop/resident-advisor-scraper) — RA events, clubs, DJs, booking contacts
- [Eventbrite Scraper](https://apify.com/crawloop/eventbrite-scraper) — city search, event URLs, organizers, ticket price range

# Actor input Schema

## `locations` (type: `array`):

City names Dice.fm lists (London, Berlin, New York) or a browse token (london-54d8a23438fe5d27d500001c).

## `startUrls` (type: `array`):

Dice.fm event (/event/), venue (/venue/), artist (/artist/), promoter (/promoters/), or city browse (/browse/) pages. Auto-detected.

## `category` (type: `string`):

Limit city browse to one Dice.fm shelf. Empty = popular feed plus every category first page (deduped).

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

Keep events starting on or after this date. Empty = no lower bound.

## `dateTo` (type: `string`):

Keep events starting on or before this date. Empty = no upper bound.

## `scrapeDetails` (type: `boolean`):

Extra request per event for description, age limit, doors, and promoter. Listing rows already include price, status, venue, and dates.

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

Hard cap across all inputs. 0 = no cap (first pages only; Dice does not expose HTML page 2).

## `monitorMode` (type: `boolean`):

Remember ids between runs and emit only NEW or CHANGED rows (price, sold-out, waiting-list, dates).

## `monitorKey` (type: `string`):

Distinct key per saved search so monitors do not share state.

## `requestDelaySecs` (type: `number`):

Throttle between HTTP requests.

## `proxyConfiguration` (type: `object`):

Public SSR pages usually work without a proxy. Enable Apify Proxy only if you hit HTTP 403/429.

## Actor input object example

```json
{
  "locations": [
    "London"
  ],
  "startUrls": [],
  "category": "all",
  "dateFrom": "",
  "dateTo": "",
  "scrapeDetails": false,
  "maxItems": 50,
  "monitorMode": false,
  "monitorKey": "default",
  "requestDelaySecs": 0.2,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

## `results` (type: `string`):

Default dataset items.

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

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

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

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,crawloop/dice-fm-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/DoY9dAKkUnCTrID3Q/builds/nh6128BDd3BWVwpf3/openapi.json
