# Resident Advisor Events API

> Electronic music events from Resident Advisor (RA) by city and date, event details and artists

- Vendor: `residentadvisoreventsapi` · version 1.0 · category Music · tags resident advisor api, ra events api, club events api, electronic music api, dj events api, nightlife api
- Datasource: custom HTTP routes
- Marketplace page: https://apiclay.com/api/residentadvisoreventsapi
- This document: https://apiclay.com/docs/residentadvisoreventsapi.md
- OpenAPI 3.1: https://apiclay.com/api/residentadvisoreventsapi/openapi.json
- MCP: connect https://api.apiclay.com/v1/mcp (see https://apiclay.com/llms.txt), then `apiclay_describe_api` with vendor `residentadvisoreventsapi`
- Updated: 2026-11-18

## About

## Resident Advisor Events API

Read Resident Advisor (ra.co), the electronic music magazine and event listings: find a city's area id, list its club events for a date range with venue, line-up, ticket flag and attendance, read one event with description, cost, minimum age, promoters and genres, and look up an artist with country, followers and bio.

Data comes from **ra.co** (https://ra.co). Every route calls the source's own public JSON endpoint (found with the live-URL scan of https://ra.co) and returns it unchanged.

Typical flow: `/areas` with `berlin` for an area id (London is 13, Berlin 34), `/events` for that area and dates, then `/event` with an event `id` and `/artist` with an artist slug.

### Routes

Every route is a POST with a JSON body `{"variables": {...}}`; the GraphQL query is fixed.

#### POST `/areas` - Area search
| Param | In | Type | Required | Description |
|---|---|---|---|---|
| variables.searchTerm | body | string | yes | City name, e.g. `berlin`. |

Returns: `data.areas[]` (`id`, `name`, `urlName`, `country`).

#### POST `/events` - Event listings
| Param | In | Type | Required | Description |
|---|---|---|---|---|
| variables.filters.areas.eq | body | number | yes | Area `id` from `/areas`. |
| variables.filters.listingDate | body | object | yes | `{"gte": "2026-11-12", "lte": "2026-11-19"}`. |
| variables.pageSize | body | number | no | Events per page. |
| variables.page | body | number | no | Page, from 1. |

Returns: `data.eventListings` (`totalResults`, `data[]` with `listingDate` and `event` (`id`, `title`, `date`, `startTime`, `endTime`, `contentUrl`, `isTicketed`, `attending`, `venue`, `artists`)).

#### POST `/event` - Event
| Param | In | Type | Required | Description |
|---|---|---|---|---|
| variables.id | body | string | yes | Event `id` from `/events`. |

Returns: `data.event` with `content` (description), `cost`, `minimumAge`, `venue` (`address`, `area`), `artists`, `promoters`, `genres`.

#### POST `/artist` - Artist
| Param | In | Type | Required | Description |
|---|---|---|---|---|
| variables.slug | body | string | yes | Artist slug from ra.co/dj/, e.g. `fourtet`. |

Returns: `data.artist` (`name`, `country`, `followerCount`, `biography.blurb`, `soundcloud`, `instagram`).

### Caveats

- Event descriptions and images belong to RA and the promoters; tickets are sold on RA.
- Upstream responses can change over time. Verify fields before relying on them.
- Not affiliated with or endorsed by ra.co.

## Pricing

- Pay as you go: 0.0012 credits/request
- Trial: 1 free requests per buyer
- Billing order: trial requests -> subscribed plan requests -> pay as you go. 1 credit's USD value is shown on the marketplace page.

## HTTP routes

Only the public, buyer-facing parts of each route are listed; vendor-side credentials stay on the gateway.

### POST /events — GET_EVENT_LISTINGS
- Gateway: `POST https://api.apiclay.com/v1/api/residentadvisoreventsapi/events`
- Body sample (JSON):

```json
{"variables": {"filters": {"areas": {"eq": 13}, "listingDate": {"gte": "2026-11-12", "lte": "2026-11-19"}}, "pageSize": 20, "page": 1}}
```

- Upstream proxy: ApiClay proxy paid by the vendor (data cap 2 MB per call). Fetched through an ApiClay proxy paid by the vendor; a response larger than the route's data cap fails with 502 and is refunded in full.

### POST /event — GET_EVENT
- Gateway: `POST https://api.apiclay.com/v1/api/residentadvisoreventsapi/event`
- Body sample (JSON):

```json
{"variables": {"id": "2578381"}}
```

- Upstream proxy: ApiClay proxy paid by the vendor (data cap 2 MB per call). Fetched through an ApiClay proxy paid by the vendor; a response larger than the route's data cap fails with 502 and is refunded in full.

### POST /artist — GET_ARTIST
- Gateway: `POST https://api.apiclay.com/v1/api/residentadvisoreventsapi/artist`
- Body sample (JSON):

```json
{"variables": {"slug": "fourtet"}}
```

- Upstream proxy: ApiClay proxy paid by the vendor (data cap 2 MB per call). Fetched through an ApiClay proxy paid by the vendor; a response larger than the route's data cap fails with 502 and is refunded in full.

### POST /areas — GET_AREAS
- Gateway: `POST https://api.apiclay.com/v1/api/residentadvisoreventsapi/areas`
- Body sample (JSON):

```json
{"variables": {"searchTerm": "berlin"}}
```

- Upstream proxy: ApiClay proxy paid by the vendor (data cap 2 MB per call). Fetched through an ApiClay proxy paid by the vendor; a response larger than the route's data cap fails with 502 and is refunded in full.

## Call example

```bash
curl -X POST "https://api.apiclay.com/v1/api/residentadvisoreventsapi/events" \
  -H "token: <YOUR_APICLAY_TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{"variables": {"filters": {"areas": {"eq": 13}, "listingDate": {"gte": "2026-11-12", "lte": "2026-11-19"}}, "pageSize": 20, "page": 1}}'
```

Index of every published API: https://apiclay.com/llms.txt
