RA APIra.co ↗
Access Resident Advisor's global database of electronic music clubs and events. List venues by city, get detailed profiles, and browse upcoming event listings.
What is the RA API?
The RA.co API exposes 3 endpoints covering Resident Advisor's worldwide database of electronic music venues and events. Use list_clubs to pull venue names, addresses, follower counts, and IDs for any supported city or country, get_club_detail to retrieve editorial descriptions, contact info, and capacity for a specific venue, and list_events to page through upcoming events with artist lineups and flyer images.
curl -X GET 'https://api.parse.bot/scraper/b89b7fc2-7fcb-49f4-8b0d-8ba592c967cc/list_clubs?area_name=berlin&country_code=de' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace ra-co-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
from parse_apis.ra_co_clubs_events_api import ResidentAdvisor, Club, ClubSummary, Event, ClubNotFound
ra = ResidentAdvisor()
# List clubs in Berlin sorted by popularity
for club in ra.clubs.search(area_name="berlin", country_code="de", limit=5):
print(club.name, club.follower_count, club.content_url)
# Get full detail for a specific club by ID
berghain = ra.club(id="5031")
for event in berghain.events.list(page_size=10, limit=3):
print(event.title, event.date, event.interested_count)
for artist in event.artists:
print(artist.name)
List all clubs/venues in a given city area on RA.co. Returns venue names, addresses, follower counts, and IDs sorted by follower count (most popular first). The full list for the requested area is returned in a single response (no pagination). Areas and country codes correspond to RA.co URL segments.
| Param | Type | Description |
|---|---|---|
| area_name | string | Area/city URL name (e.g., 'washingtondc', 'paris', 'berlin', 'london'). |
| country_code | string | Country URL code (e.g., 'us', 'fr', 'uk', 'de'). |
{
"type": "object",
"fields": {
"area": "string — area name as passed in the request",
"clubs": "array of club summary objects with keys: id, name, address, content_url, follower_count, is_closed, logo_url",
"country": "string — country code as passed in the request",
"total_clubs": "integer — total number of clubs returned"
},
"sample": {
"data": {
"area": "berlin",
"clubs": [
{
"id": "5031",
"name": "Berghain | Panorama Bar | Säule",
"address": "70 Am Wriezener Bahnhof; Friedrichshain; 10243 Berlin; Germany",
"logo_url": "https://static.ra.co/images/clubs/berghain-berlin-logo.jpg?dateUpdated=1610108248310",
"is_closed": null,
"content_url": "/clubs/5031",
"follower_count": 45211
}
],
"country": "de",
"total_clubs": 2275
},
"status": "success"
}
}About the RA API
Venue Discovery by City
The list_clubs endpoint accepts an area_name (such as 'berlin' or 'washingtondc') and an optional country_code to return all venues RA tracks in that area. Each item in the clubs array includes the venue's id, name, address, follower_count, is_closed flag, and logo_url. Results are sorted by follower count, so the most-followed venues surface first. The total_clubs field tells you how many venues were found in that area.
Venue Profiles
get_club_detail takes a single club_id (for example, '1672' for Rex Club Paris or '6751' for Berghain Berlin) and returns a richer profile. Fields include the editorial blurb, phone, full address, website, and capacity. Nested area and country objects carry structured IDs and URL slugs, which you can feed back into other requests or use for display grouping.
Event Listings with Pagination
list_events returns upcoming events for a given venue, filtered by club_id. You can set a date_from in ISO format to start from a specific point in time, control page size up to 50 with page_size, and walk through results using the page parameter. Each event object in the events array carries id, title, date, start_time, content_url, interested_count, flyer_url, and an artists array, alongside nested venue, area, and country objects for full context.
The RA API is a managed, monitored endpoint for ra.co — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when ra.co changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official ra.co API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Build a city nightlife guide that ranks clubs by
follower_countfromlist_clubs. - Aggregate upcoming event lineups across multiple venues using
list_eventswithdate_fromfiltering. - Display venue contact details and capacity on a booking platform using
get_club_detail. - Track which venues are permanently closed using the
is_closedflag returned bylist_clubs. - Power a flyer gallery for an event-discovery app using
flyer_urlfromlist_eventsresponses. - Map electronic music clubs geographically using
addressandareadata from venue endpoints. - Monitor event
interested_countover time to gauge crowd demand for specific club nights.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Resident Advisor have an official public developer API?+
What does `list_clubs` return beyond basic venue names?+
list_clubs returns an array of venue objects, each containing id, name, address, content_url, follower_count, is_closed, and logo_url. Results are ordered by follower_count descending, so you can immediately identify the most-followed venues in an area without any client-side sorting.Can I retrieve past events or only upcoming ones?+
list_events defaults to the current UTC time as its start point and returns upcoming events. Historical event archives are not currently exposed. You can fork this API on Parse and revise it to add an endpoint targeting past event data.Does the API cover artist profiles or DJ charts?+
list_clubs and get_club_detail, and upcoming events via list_events. Artist profiles, DJ charts, and record label data are not included. You can fork the API on Parse and revise it to add endpoints for those data types.Are all cities and countries supported by `list_clubs`?+
area_name slug (such as 'london' or 'paris') and a country_code to scope results. Areas where RA has no indexed venues will return an empty clubs array. Smaller or less-documented cities may have limited or no results.