Luma calendar

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

A Luma calendar (an organiser's page): name, description, avatar, cover, website and social handles, location, verified flag, and its upcoming or past events (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
slug string The calendar's lu.ma/<slug>. Example: fdotinc
url string Or the lu.ma calendar link.
id string Or the calendar id (cal-...).
period future | past Upcoming (default) or past events.
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/calendar?slug=fdotinc" \
  -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.