# RA Events Scraper — Resident Advisor Concerts (`memo23/ra-events-scraper`) Actor

Scrape electronic music events from ra.co (Resident Advisor) — artist, venue, address, coordinates, date, lineup and ticket status. Works with any city/area or direct event URL. JSON or CSV out.

- **URL**: https://apify.com/memo23/ra-events-scraper.md
- **Developed by:** [Muhamed Didovic](https://apify.com/memo23) (community)
- **Categories:** Social media
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $10.00 / 1,000 scraped items

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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

## RA Events Scraper — Resident Advisor (ra.co) Concerts & Club Nights

<p align="center"><img src="https://raw.githubusercontent.com/muhamed-didovic/muhamed-didovic.github.io/main/assets/ra-events-logo.png" width="140" alt="RA Events Scraper"></p>

Scrape electronic music events from **ra.co** (Resident Advisor) — artist lineup, venue, address, coordinates, date, cost, and ticket status for every event. Works with any city/area or direct event URL. One row per event, clean JSON out.

***

### Why use this scraper

- **Full event detail.** Title, date, start/end time, entry cost, ticket status, venue (name, address, lat/lng), full artist/DJ lineup with profile links, and promoters.
- **City or area input.** Paste a city name (`berlin`), an area page URL, a numeric area ID, or direct event URLs — all auto-resolved via the GraphQL API.
- **No login, no API key.** Uses RA's public GraphQL endpoint — no credentials needed.
- **Structured output.** Clean flat rows — ready for spreadsheets, databases, or LLM pipelines.
- **Fast.** GraphQL pagination fetches 50 events per request; 1798 Berlin events in seconds.

***

### Overview

Resident Advisor (ra.co) is the world's leading electronic music platform — club nights, festivals, and DJ events worldwide. This actor queries RA's GraphQL API for event listings by area, returning structured data: who's playing, where, when, what it costs, and where to buy tickets.

Each output row is a single event with the full artist lineup, the venue (name, address, geo coordinates), the timing (start/end), cost, ticket status, and promoters.

***

### Supported inputs

- **Area names** (resolved to IDs via GraphQL):
  - `berlin`
  - `london`
  - `tokyo`
- **Area page URLs**:
  - `https://ra.co/events/berlin`
  - `https://ra.co/events/london`
- **Numeric area IDs**:
  - `34` (Berlin)
  - `1` (London)
- **Direct event URLs**:
  - `https://ra.co/events/2537180`

Mix and match — pass multiple area names or URLs in `startUrls`.

***

### Use cases

- **Club night database** — build a directory of electronic music events by city.
- **Venue research** — collect venue names, addresses, and coordinates for a region.
- **Lineup tracking** — monitor which DJs are playing where.
- **Music-industry leads** — promoters and venues for outreach.
- **Genre analysis** — what's being programmed in which cities.
- **Travel planning** — find club nights in a city you're visiting.

***

### How it works

<p align="center"><img src="https://raw.githubusercontent.com/muhamed-didovic/muhamed-didovic.github.io/main/assets/how-it-works-ra-events.png" width="900" alt="How it works"></p>

1. You provide area names, area URLs, or direct event URLs.
2. The actor resolves area names to area IDs via RA's GraphQL `areas` query.
3. It paginates through the `eventListings` GraphQL query (50 events per page).
4. Each event becomes one clean row in the dataset — no HTML scraping needed.

***

### Input

| Field | Type | Default | Notes |
|---|---|---|---|
| `startUrls` | array | Berlin | RA URLs, area names, area IDs, or event URLs. All auto-resolved. |
| `maxItems` | integer | 1000 | Maximum events to scrape. |
| `maxConcurrency` | integer | 10 | How many GraphQL pages to fetch in parallel. |
| `proxy` | object | Apify proxy | Proxy configuration. |

```json
{
  "startUrls": ["berlin", "london"],
  "maxItems": 500
}
```

***

### Output

One row per event:

```json
{
  "type": "event",
  "eventId": 2539790,
  "eventUrl": "https://ra.co/events/2539790",
  "title": "Pulse Friction × FLIGHTMODE",
  "date": "2026-10-03T00:00:00.000",
  "startTime": "2026-10-03T19:00:00.000",
  "endTime": "2026-10-04T04:00:00.000",
  "cost": "10",
  "isTicketed": true,
  "venueName": "Madame Claude",
  "venueUrl": "https://ra.co/clubs/28667",
  "venueAddress": "Lübbener Str. 19, 10997 Berlin, Germany",
  "coordinates": { "latitude": 52.499504, "longitude": 13.437223 },
  "artists": [
    { "name": "doctor doms", "url": "https://ra.co/dj/doctordoms" },
    { "name": "Dr. Sud", "url": "https://ra.co/dj/dr.sud" }
  ],
  "promoters": [],
  "areaId": "34",
  "areaName": "Berlin"
}
```

#### Key output fields

- **`eventId`** — RA's numeric event ID, stable across runs.
- **`title` / `date` / `startTime` / `endTime`** — event timing.
- **`cost` / `isTicketed`** — entry cost and whether tickets are sold via RA.
- **`venueName` / `venueUrl` / `venueAddress` / `coordinates`** — full venue details.
- **`artists`** — array of `{ name, url }` for each artist/DJ in the lineup.
- **`promoters`** — array of `{ name }` for event promoters.
- **`areaId` / `areaName`** — which RA area the event was scraped from.

***

### FAQ

**Do I need an RA account or API key?**
No. The scraper uses RA's public GraphQL endpoint, which requires no authentication.

**How are area names resolved?**
The actor calls RA's `areas(searchTerm:)` GraphQL query to find the matching area ID. For example, "berlin" resolves to area ID 34.

**How many events can I scrape?**
Berlin alone has ~1800 upcoming events. The actor paginates through all of them, capped by `maxItems`. Large multi-city runs can return tens of thousands of events.

**Can I scrape multiple cities?**
Yes — pass multiple area names or URLs in `startUrls`.

***

### ⚠️ Disclaimer

This Actor scrapes publicly available event data from ra.co. It does not access authenticated or private content, and collects no personal data. You are responsible for using the output in line with Resident Advisor's terms and any applicable law in your jurisdiction. This Actor is not affiliated with, endorsed by, or sponsored by Resident Advisor.

***

### SEO Keywords

ra.co scraper, resident advisor scraper, electronic music events api, club night scraper, dj events scraper, ra events export, techno events scraper, house music events, club listings scraper, electronic music database, dj lineup scraper, venue scraper, club event data, ra.co data extraction, electronic music api, club night database, festival scraper, dj booking data, music event feed, ra csv export, club coordinates, electronic event calendar

# Actor input Schema

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

RA URLs or area identifiers. Area pages (https://ra.co/events/berlin), area names ('berlin'), numeric area IDs ('34'), or direct event URLs (https://ra.co/events/2537180) are all accepted. Areas are resolved to IDs via the GraphQL API.

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

Maximum number of events to scrape.

## `maxConcurrency` (type: `integer`):

How many pages to fetch in parallel (GraphQL).

## `proxy` (type: `object`):

Apify proxy to use. Defaults to the Apify residential proxy pool.

## Actor input object example

```json
{
  "startUrls": [
    {
      "url": "https://ra.co/events/berlin"
    }
  ],
  "maxItems": 1000,
  "maxConcurrency": 10,
  "proxy": {
    "useApifyProxy": true
  }
}
```

# Actor output Schema

## `results` (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 = {
    "startUrls": [
        {
            "url": "https://ra.co/events/berlin"
        }
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("memo23/ra-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 = { "startUrls": [{ "url": "https://ra.co/events/berlin" }] }

# Run the Actor and wait for it to finish
run = client.actor("memo23/ra-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 '{
  "startUrls": [
    {
      "url": "https://ra.co/events/berlin"
    }
  ]
}' |
apify call memo23/ra-events-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,memo23/ra-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/RfpGGccXrLHFxpzwy/builds/78FyM4JLFSca3cAfH/openapi.json
