Luma events near a place

GET https://api.api.sh/luma/v1/events
1 credit / call travel & events try it in the playground →

Upcoming Luma events in a discover city or around a map point, optionally in one category. Each event: id, name, link, start and end, timezone, in person or online, place (address when public, city, region, country, coordinates), cover, free flag and price range, sold-out flag, spots left, approval needed, waitlist, guest count, calendar and hosts. Pass next_cursor back as cursor.

Every response includes credits_used: the credits this call cost.

Parameters

nametypedescription
place string A discover city slug from /luma/v1/discover (e.g. sf, nyc, london, berlin, singapore) or its discplace- id. Example: sf
latitude string Or a map point: latitude.
longitude string Map point longitude.
category string A category slug from /luma/v1/discover, e.g. ai, tech, arts, climate, fitness, wellness, crypto, food.
limit integer Results per page (default 25, max 50).
cursor string Pass next_cursor from the previous response; null on the last page.

Every endpoint also takes fresh, raw, fields (see lean responses and caching).

Example

curl "https://api.api.sh/luma/v1/events?place=sf" \
  -H "x-api-key: $APISH_KEY"

Response

A JSON object with the fields described above, plus raw (the source's own data), cached, fetched_at and credits_used. Errors return {"success": false, "error": "…"} with the HTTP status (see errors). A lookup that ran but found nothing (404) costs the price above; refused calls and errors on our side are free (what's charged).

The fastest way to see the full response is the playground: it runs this endpoint with your account and shows the exact JSON.