# Luma Events Discovery API

> Upcoming public events on Luma by city or coordinates, with hosts, times, venues and categories

- Vendor: `lumaeventsdiscoveryapieoj54` · version 1.0 · category Entertainment · tags luma api, lu.ma api, events api, tech events api, meetups api, event discovery api
- Datasource: custom HTTP routes
- Marketplace page: https://apiclay.com/api/lumaeventsdiscoveryapieoj54
- This document: https://apiclay.com/docs/lumaeventsdiscoveryapieoj54.md
- OpenAPI 3.1: https://apiclay.com/api/lumaeventsdiscoveryapieoj54/openapi.json
- MCP: connect https://api.apiclay.com/v1/mcp (see https://apiclay.com/llms.txt), then `apiclay_describe_api` with vendor `lumaeventsdiscoveryapieoj54`
- Updated: 2026-11-18

## About

## Luma Events Discovery API

Public discovery data from Luma (lu.ma), the event platform used for tech meetups, community events and conferences: upcoming events in a city or near a latitude and longitude, paged with a cursor, each with name, start and end times, timezone, location type, address when public, cover image, hosts, guest and ticket info and the event URL slug; the list of discover cities with their ids; event categories with event counts; and featured calendars.

Data comes from **lu.ma** (https://lu.ma). Every route calls the source's own public API and returns it unchanged.

Typical flow: `/places` for a city id, then `/events?discover_place_api_id=&amp;pagination_limit=20` (or `/events?latitude=40.71&amp;longitude=-74.0`); follow `next_cursor` with `pagination_cursor`.

### Routes

#### GET `/events` - Events
| Param | In | Type | Required | Description |
|---|---|---|---|---|
| discover_place_api_id | query | string | no | City id from `/places`, e.g. `discplace-CzipmKodUYN2Dfx` (New Delhi). |
| latitude | query | number | no | Latitude for events near a point (use with `longitude`). |
| longitude | query | number | no | Longitude. |
| pagination_limit | query | number | no | Events per page. |
| pagination_cursor | query | string | no | `next_cursor` from the previous page. |

Returns: `entries` array, each with `event` (`api_id`, `name`, `start_at`, `end_at`, `timezone`, `location_type`, `geo_address_info` when public, `coordinate`, `cover_url`, `url` slug for lu.ma/), `calendar`, `hosts` (public profiles), `featured_guests`, `guest_count`, `ticket_info`, `registration_availability`; plus `has_more` and `next_cursor`.

#### GET `/places` - Places
No parameters.

Returns: `places` (about 90 discover cities, each `place` with `api_id`, `name`, `description`, `coordinate`), `featured_place`, `calendars` and `categories`. About 120 KB.

#### GET `/categories` - Categories
| Param | In | Type | Required | Description |
|---|---|---|---|---|
| pagination_limit | query | number | no | Categories per page. |
| pagination_cursor | query | string | no | `next_cursor` from the previous page. |

Returns: `entries` array: `api_id` and `category` (`name`, `description`, `event_count`, images); plus `has_more` and `next_cursor`.

#### GET `/calendars` - Featured calendars
No parameters.

Returns: `major_calendars` and `global_calendars`: featured community calendars with name, description, slug and images.

### Caveats

- Events carry host profiles and, when the host shows the guest list, `featured_guests` with attendees' names and social handles, exactly as Luma's site shows them; handle that personal data under the GDPR and other applicable law.
- Times are ISO 8601 in UTC, with the event's `timezone`.
- Upstream responses can change over time. Verify fields before relying on them.
- Not affiliated with or endorsed by lu.ma.

## 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.

### GET /events — Events
- Gateway: `GET https://api.apiclay.com/v1/api/lumaeventsdiscoveryapieoj54/events`
- Public query params: `discover_place_api_id` (string), `latitude` (number), `longitude` (number), `pagination_limit` (number), `pagination_cursor` (string)
- 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.

### GET /places — Places
- Gateway: `GET https://api.apiclay.com/v1/api/lumaeventsdiscoveryapieoj54/places`
- 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.

### GET /categories — Categories
- Gateway: `GET https://api.apiclay.com/v1/api/lumaeventsdiscoveryapieoj54/categories`
- Public query params: `pagination_limit` (number), `pagination_cursor` (string)
- 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.

### GET /calendars — Featured calendars
- Gateway: `GET https://api.apiclay.com/v1/api/lumaeventsdiscoveryapieoj54/calendars`
- 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 GET "https://api.apiclay.com/v1/api/lumaeventsdiscoveryapieoj54/events" \
  -H "token: <YOUR_APICLAY_TOKEN>"
```

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