Resident Advisor Events Scraper

Scrape Resident Advisor (ra.co) event listings for any city and date range via RA's official GraphQL API. No login, no external proxy key — runs on Apify RESIDENTIAL proxy out of the box. Pay per result.

What you get (one record per event)

Field	Description
eventId	Stable RA event ID
title	Event name
date	Listing date
startTime / endTime	Start & end timestamps
venue / venueUrl / venueId	Venue name, RA page, stable ID
artists	Full lineup as a comma-separated string
artistList / artistIds	Lineup as a list + stable artist IDs
guestsAttending	Number of people marked attending (demand signal)
isTicketed	Whether the event sells tickets on RA
flyer	Event flyer image URL
raPickBlurb	RA editorial "pick" blurb, when present
url	Event page URL
scrapedAt	When this record was scraped

The fields above the line match what other RA scrapers emit; artistList, artistIds, venueId, guestsAttending, isTicketed, flyer and raPickBlurb are the extras this actor adds.

Input

Field	Type	Notes
area	integer	Required. RA area (city) code. Find it in the ra.co events URL — ra.co/events/uk/london is 13. e.g. London 13, New York 8, Berlin 34, Amsterdam 23.
startDate	string	YYYY-MM-DD, inclusive. Default: today (UTC).
endDate	string	YYYY-MM-DD, inclusive. Default: startDate + 7 days.
maxItems	integer	Cap on events. Default 100. 0 = no limit.
proxyConfiguration	proxy	Default Apify RESIDENTIAL.

Example

{
  "area": 13,
  "startDate": "2026-06-18",
  "endDate": "2026-06-25",
  "maxItems": 100
}

How it works

Posts the GET_EVENT_LISTINGS operation to https://ra.co/graphql (RA's own public web API), paginates the area + date range, and flattens each event into a flat record. Requests are routed through a residential proxy and retried with backoff on rate-limit / transient network errors.

Notes

• Area codes are RA's internal city IDs — copy them from the ra.co events URL.
• guestsAttending reflects RA's "attending" count at scrape time.
• Billing event: event-listing (one charge per event record).

Usage statistics

This Actor creates a small, content-free summary at the end of each run. It is used only to monitor reliability and improve this Actor. A copy is saved as USAGE_STATS in your own Apify key-value store, so you can see the exact record created for your run.

Set disableUsageStats to true in the input to opt out. Nothing is sent then; your USAGE_STATS record only says that statistics were disabled.

Only these fields are recorded:

• schema version, Actor name and build number;
• UTC start and finish hour (not a precise timestamp);
• run duration, number of results and time to the first result, each as a coarse range;
• whether the result was empty, the end status, and an error type from a fixed list;
• memory setting and counts of charged events;
• names of the input fields you set, never their values;
• the selected option for input fields that offer a fixed list of choices (for example a sort order).

We do not collect input text, search terms, URLs, domains, usernames, email addresses, names, proxy credentials, tokens, scraped records, output items, raw error messages, stack traces, or hashes of any of those values. Records are kept for no longer than 13 months, used only as aggregated operational statistics, and never sold or shared.

Additional fields (Phase 2)

This Actor also records your Apify user ID, whether Apify marks the account as paying, the size range of list inputs, the selected country when the input offers a fixed list of countries, and one category from a fixed Actor taxonomy. We use these fields only for aggregate reliability, repeat-use and cross-Actor analysis; reports suppress any cell with fewer than five distinct users.

The same disableUsageStats: true input flag turns these fields off too. The user ID is removed after 13 months; we do not export, sell, share, or attempt to re-identify this data.