Luma Events API — Events by City, Category & Calendar

Every upcoming Luma (lu.ma) event in a city, a category or a calendar, as clean rows: name, start and end time, timezone, venue and address, city and coordinates, price and currency, sold-out and waitlist state, spots left, guest count, and the organising calendar. Turn on details for each event's description (plain text or Markdown), ticket types and categories. Filter by keyword, date window, in person or online, and free only. No login, no browser, no key — and no host's name, handle or photo, ever.

Luma is where a large share of tech, AI and startup meetups are listed now, and it serves its event data as JSON to every visitor. This Actor reads that JSON — the same data Luma's own pages are built from — rather than the HTML around it.

At a glance

Input — this is the Store prefill; paste it and run:

{ "mode": "place", "places": ["sf"], "maxEventsPerSource": 25 }

The next 25 events in San Francisco, soonest first, plus one free row describing what was read. It is one 145 KB request.

Output — one row per event; the fields you will use most are name, startAt, venueName, address, city, isFree, price, registrationStatus, guestCount, calendarName and url (full list under Output reference). Anything that could not be read — an unknown city, a private event, a blocked request — comes back as a free diagnostic row (rowType: "diagnostic", errorType, error) instead of a charge.

Price — $1.00 per 1,000 events on the FREE tier (+ $0.001 per run, charged only once a run has returned an event). City, category, source and diagnostic rows are free, so are events your filters exclude, and a run that returns nothing bills nothing at all. Pay per event, limited permissions — works over the Apify MCP server (mcp.apify.com) and with agentic (x402) payments.

From code — client.actor("insight.solutions/luma-events-api").call(run_input={…}) with apify-client, or

POST https://api.apify.com/v2/acts/insight.solutions~luma-events-api/run-sync-get-dataset-items

Who it is for

• Event marketers and community teams — every AI, crypto or climate event in the cities you cover, with dates, venues, capacity and the communities running them, refreshed on a schedule.
• Sponsorship and partnerships — which organisations host the most events, how full they get (guestCount, isSoldOut, waitlist), and where.
• Researchers and newsletters — a week's or a month's events in a city as one table (startAfter / startBefore), with Markdown descriptions ready to summarise.
• Founders and job seekers — the meetups worth going to, filtered to free and in person.

What you get

An event (from the San Francisco prefill; null columns cut):

{
  "ok": true,
  "rowType": "event",
  "input": "sf",
  "source": "place:sf",
  "sourceUrl": "https://api.lu.ma/event/get?event_api_id=evt-D083fftWbb5Dpqv",
  "eventId": "evt-D083fftWbb5Dpqv",
  "slug": "init-conf",
  "url": "https://luma.com/init-conf",
  "name": "init() by WorkOS",
  "startAt": "2026-10-07T15:00:00Z",
  "endAt": "2026-10-08T00:00:00Z",
  "timezone": "America/Los_Angeles",
  "locationType": "offline",
  "venueName": "SFJAZZ",
  "address": "SFJAZZ, 201 Franklin St, San Francisco, CA 94102, USA",
  "city": "San Francisco",
  "region": "California",
  "country": "United States",
  "countryCode": "US",
  "latitude": 37.7764351,
  "longitude": -122.421631,
  "addressVisibility": "public",
  "coverUrl": "https://images.lumacdn.com/uploads/bt/3bcd166d-cf3c-4d92-af57-2686f9de44da.gif",
  "isFree": true,
  "isSoldOut": false,
  "isNearCapacity": false,
  "requireApproval": true,
  "registrationStatus": "open",
  "waitlist": false,
  "guestCount": 0,
  "ticketCount": 0,
  "hostCount": 1,
  "verifiedHostCount": 0,
  "calendarKind": "organization",
  "calendarId": "cal-Z1tslEBMjjCh4fd",
  "calendarName": "WorkOS Events",
  "calendarWebsite": "https://workos.com",
  "calendarAvatarUrl": "https://images.lumacdn.com/calendars/xz/a7cb4c75-9cbd-4853-8012-496c5ef3eb77.png",
  "rank": 1
}

A paid, sold-out one:

{
  "name": "NeoCloud Summit 2026 — Where the Next Cloud Gets Built",
  "isFree": false,
  "price": 995,
  "currency": "USD",
  "isSoldOut": true,
  "spotsRemaining": 0,
  "registrationStatus": "sold-out",
  "calendarName": "Ignite Community"
}

An event whose organiser shows the address to registered guests only — the city is given, the street is not, and Luma's approximate point is rounded:

{
  "name": "Hardware hackathon: turn a vintage toy into a voice agent",
  "venueName": null,
  "address": null,
  "city": "San Francisco",
  "latitude": 37.8,
  "longitude": -122.4,
  "addressVisibility": "guests-only"
}

With includeDetails (and always in events mode) the row also carries the description, ticket types and the rest:

{
  "description": "WorkOS presents [**init(): the conference for builders**](https://workos.com/init).  \n\nJoin the founders, engineers, and technical leaders shaping what’s next. …",
  "descriptionFormat": "markdown",
  "categories": ["AI"],
  "ticketTypes": [{ "name": "Standard", "type": "free", "price": null, "registered": 1060, "requireApproval": true, "isHidden": false }],
  "sessionCount": 0,
  "faqCount": 0,
  "registrationQuestionCount": 7,
  "locale": "en"
}

And one free source row per city, category or calendar, saying what was read: eventsFound, eventsReturned, eventsFiltered, duplicatesSkipped, pages, capReached and hasMore.

Quick start

1. Pick What to read: cities, categories, calendars, or single events.
2. Fill that list — sf, https://lu.ma/ai, a calendar's link, event links. Don't know the slug? Run mode discover once: it lists every city and category Luma has, with its id and slug, free.
3. Optionally narrow it: Keyword, Starting on or after / before, In person or online, Free events only.
4. Turn on Include details for descriptions and ticket types, set Max events per source, and run. Rows arrive soonest first.

Input

Links on lu.ma and luma.com are both accepted (lu.ma now redirects to luma.com, so every url in the output is a luma.com link). Duplicates are dropped on what they resolve to, so sf, https://lu.ma/sf and its discplace- id are one city.

A run with nothing usable to read — an empty list for the chosen mode, entries that are not Luma's, a date that is not a date, startAfter not before startBefore — finishes FAILED before a single request, with a free row saying which entry was the problem. A date typo is refused rather than ignored, so it can never turn a filtered run into an unfiltered (and billed) one.

Output reference

Every row has the same columns, null where a column does not apply, so the dataset exports as one table.

On every row: ok, rowType (event · place · category · source · diagnostic), input (your entry, as typed), error, errorType, scrapedAt, source (place:sf, category:ai, calendar:cal-…, event, discover), sourceUrl.

Events:

Place and category rows (free, discover mode): placeId or categoryId, slug, name, url, eventCount, timezone, latitude, longitude and description for cities; upcomingEventCount for categories.

Source rows (free, one per source): eventsFound, eventsReturned, eventsFiltered, duplicatesSkipped, pages, capReached, hasMore, plus the city's, category's or calendar's id and name.

Diagnostic rows (free):

How Luma is read

Each source gets one request in flight, 250–600 ms apart, through its own proxy session, however many sources run at once (in events mode, the links one worker reads share its session and its pacing). A city or calendar walk stops as soon as Luma's events pass your startBefore, since Luma lists them by start time. luma.com/robots.txt is read once per run, before the first page, and every rule in it is honoured for this Actor too — including the ones it addresses only to one search engine's crawler (/in/, /company/, /session-*, /social-share). A run that reads no page (a city in the catalog, a calendar or event by id) never fetches it.

Host names are never included. Luma's event data lists the people hosting each event — names, usernames, photos, bios, social handles — and the guests it features. This Actor never copies any of them: you get hostCount and verifiedHostCount, and nothing else about a person. A calendar is identified only when Luma marks it as an organisation's; a person's own calendar comes back as calendarKind: "personal" with its name, link and picture left out, and a calendar source of that kind is labelled calendar:personal. Payment accounts, coupon codes, tracking pixels and crypto-wallet requirements are never read into a row, and registration questions are only counted. Event names, descriptions and venue addresses are the organiser's published copy and are returned as Luma serves them.

What you are never charged for

• Every place, category and source row.
• Every diagnostic row: unknown cities, private or removed events, blocked requests, timeouts, pages Luma changed, paths robots.txt disallows.
• Events your filters exclude — keyword, dates, in person or online, free only.
• An event reached a second time in a run, from another source or another page (it is a duplicate, counted on the source row).
• The detail request behind includeDetails: same price per event.
• A run that returns nothing at all: it finishes SUCCEEDED with zero results and a "0 results … Nothing was charged." status message naming the diagnostic rows by type, and bills nothing, start fee included.

Pricing

$1.00 per 1,000 events.

Charging is charge-after-push: rows are in your dataset before the event is recorded. ACTOR_MAX_TOTAL_CHARGE_USD is respected — the run stops fetching when it is reached and finishes SUCCEEDED saying so.

Proxy

The default is { "useApifyProxy": true } — Apify's datacenter pool. The capture probe read every endpoint above through it. A 403 or 429 is treated as a block: that source's proxy session is rotated once, and a second refusal becomes a free blocked row rather than a retry loop. A JSON 403 from Luma itself (a private event) is reported as not-found straight away — asking again from another address would not change the answer. If blocked rows become common, switch proxyConfiguration to residential.

Use it from an AI agent, or from code

One JSON object in, one flat array out — the shape agent runtimes want. The Actor runs with limited permissions, uses pay-per-event pricing and never enters Standby, so it works over the Apify MCP server and with x402 agentic payments. The Integrations tab pushes results to Slack, a webhook, Zapier, Make, Google Sheets, Snowflake or BigQuery.

curl -X POST "https://api.apify.com/v2/acts/insight.solutions~luma-events-api/run-sync-get-dataset-items?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"mode":"place","places":["sf","nyc"],"keyword":"AI","startAfter":"2026-11-01","startBefore":"2026-12-01","maxEventsPerSource":100}'

# pip install apify-client
from apify_client import ApifyClient

client = ApifyClient("<APIFY_TOKEN>")
run = client.actor("insight.solutions/luma-events-api").call(run_input={
    "mode": "category",
    "categories": ["ai", "climate"],
    "freeOnly": True,
    "includeDetails": True,
    "descriptionFormat": "markdown",
})

for row in client.dataset(run["defaultDatasetId"]).iterate_items():
    if row["rowType"] == "event":
        print(row["startAt"], row["city"], row["name"], row["calendarName"], row["url"], sep=" | ")
    elif row["rowType"] == "diagnostic":
        print("could not read", row["input"], row["errorType"], row["error"])

Building an app with Lovable? Apify's Lovable connector runs any Actor from inside a Lovable project with your Apify token. Connect Apify in Lovable once, then ask it: "Use Apify to run insight.solutions/luma-events-api for my city and build an events calendar around the results." At the default settings a run finishes well inside Lovable's 300-second synchronous limit, and every result is one JSON object per row, so the generated app needs no extra parsing. Usage bills to the Apify account whose token is connected.

FAQ

Do I need a Luma account or an API key? No. Only what Luma shows any visitor is read.

How do I find a city's or category's slug? Run mode: "discover" once. It returns every city (87 when this was written) and category (12) with its id, slug and event count, as free rows.

Is a category every event Luma tags with it? No — and this is worth knowing. A Luma category page lists calendars (communities and conference calendars), not events, so category mode returns the upcoming events of the calendars the category page features, merged by start time. For "every AI event in a city", use place mode with keyword: "AI", and turn on includeDetails to search descriptions too.

Why is address empty for some events? The organiser chose to show it to registered guests only. The city, region and country are still given, and an approximate point rounded to about a kilometre.

Why are host names missing? By design: hosts are people, and only their count is returned. Organisation calendars are identified by name; a person's own calendar is not.

Does startAfter use UTC? A bare date is a day in each event's own timezone, so 2026-11-01 keeps a 7 pm talk in San Francisco on 1 November even though it is 2 November in UTC. A full timestamp is exact.

How many events can I get? Up to 10,000 per source and 100,000 per run. A source stops after reading 5,000 events, so a narrow filter on a very large calendar may not reach its end; its source row then says Luma had more.

Limitations

• Category mode reads the calendars a category page features, not a full category index (see the FAQ). Luma offers no category event list to visitors; the endpoint that looks like one answers 404.
• Upcoming events only in place, category and calendar modes: the lists Luma serves start from now.
• includeDetails costs one request per event, paced at 250–600 ms within a source: one to two events a second per source. Several sources run at once (maxConcurrency); raise maxRunSecs for large detailed runs — the default 240 seconds covers a few hundred detailed events per source.
• Host names are never included, by design (see How Luma is read).
• Prices are read as Luma's cents divided by 100. Currencies without minor units have not been seen in a capture yet.
• The upstream format may change: this Actor reads Luma's JSON as it is served today, leaves a column null when an event does not carry it, and returns a free parse-failed row rather than a wrong one when a page no longer has the data it expects.
• Not affiliated with Luma. "Luma" is used only to say whose public event pages are read.

Related: to keep only the new events of a calendar between runs, put this Actor on a schedule and compare eventIds; to read an event's own website, use Website to Markdown — Content Extractor for LLMs & RAG.

Our other Actors

Every Insight Solutions Actor is pay-per-result with no browser, no login and no API key, and every one of them returns free diagnostic rows instead of billing for failures. Prices are per 1,000 results.

Video, audio & social

• YouTube Transcript API — captions as timed segments, text, SRT or VTT, with language fallback and translation.
• YouTube Comments API — comments and replies with likes, pinned and hearted flags, newest or top sort.
• YouTube Channel API — a channel's videos, Shorts and live streams, plus YouTube search.
• Podcast Search, Episodes & Charts API — Apple Podcasts search, charts and full episode feeds.
• Bluesky Scraper — profiles, posts, followers and follows from the public AT Protocol API.
• Telegram Channel Scraper — posts, views and channel stats from public Telegram channels.
• Substack Scraper — posts with full free text, comments and publication profiles.
• Hacker News API — stories, comments, users, front page and a structured "Who is hiring?" parser from the official HN APIs.
• GitHub Repos, Trending & Releases API — repository facts, trending lists, releases and search, no token needed for small runs.
• Discourse Forum API — topics, posts and categories from any Discourse community via its own JSON endpoints, usernames only.

News, documents & the web

• Google News Search, Topics & Real Article URLs — news search and topic feeds with the publisher's real URL decoded.
• Website to Markdown — Content Extractor for LLMs & RAG — any site as clean Markdown, text and heading-aware chunks.
• WordPress Posts & Pages API — posts and pages from any WordPress site as clean text or Markdown, with categories, tags and images.
• Website Metadata API — any URL's meta tags, Open Graph, Twitter cards, hreflang, feeds, JSON-LD and microdata, with normalised Product, Article, Event and FAQ entities.
• Subdomain Finder API — every subdomain of a domain from certificate-transparency logs, resolved over DNS, with an optional live HTTP check.
• Internet Archive API — archive.org search, item metadata, files and reviews.
• Wayback Machine Toolkit — archived URL inventories, snapshots and text diffs between dates.
• Website Technology Detector — the tech stack behind any site, with the evidence for each detection.
• Domain Intelligence API — DNS, RDAP registration, TLS certificate and HTTP facts in one row per domain.
• SEO Page Audit — sitemap crawl with on-page checks, structured data and broken-link reports.
• Keyword Suggestions API — Google, YouTube, Bing, Amazon and eBay autocomplete with alphabet and question expansions.
• Website Contact Extractor — emails, phone numbers and social profiles from any list of websites.
• Web Search Results API — Bing and DuckDuckGo organic results with snippets, no key, no browser.
• Company Enrichment API — a domain in, a company profile out: firmographics, contacts, tech stack, DNS and hiring signal.
• Company Dossier API — one company in, twelve sections out: profile, tech, contacts, DNS, open roles, news, SEC filings, federal awards, recalls, YC batch and apps.
• Press Releases API — GlobeNewswire and PR Newswire releases plus any newsroom feed, by keyword, company, ticker or subject.
• Federal Register API — rules, proposed rules, notices and the Public Inspection desk with dockets, comment deadlines and CFR references.
• Academic Papers Search API — OpenAlex, Crossref, arXiv and PubMed in one row per paper: abstract, citations, open-access PDF, authors and venue.
• RSS & Atom Feed Monitor — any RSS, Atom or JSON feed (or an OPML file) in, only the new items out, with keyword filters and a webhook.
• Website Change Monitor — watch any pages, diff the text between runs, get change rows with added/removed lines, keyword alerts and a webhook.
• Wikipedia & Wikidata API — article text, search, daily pageviews and Wikidata entity facts, any language edition.

Business, finance & jobs

• Congress & Insider Trades API — STOCK Act periodic transaction reports and SEC Form 4 insider trades in one schema.
• Federal Contracts, Grants & Lobbying API — SAM.gov opportunities, USAspending awards, Grants.gov notices and Senate lobbying filings in one schema.
• SEC EDGAR API — filings, XBRL financials and full-text search by ticker or CIK.
• Clinical Trials & FDA API — ClinicalTrials.gov studies plus openFDA recalls, labels, approvals, 510(k)s and adverse-event reports.
• Product & Vehicle Recalls API — CPSC, NHTSA, FDA and USDA recalls, vehicle complaints and ratings, plus a VIN decoder.
• Y Combinator Companies, Batches & Founders — the YC directory with founders and social links, filterable by batch, industry and hiring status.
• Career Site Jobs API — jobs straight from Greenhouse, Lever, Ashby, Workable and 10+ other ATS career sites.
• Workday Jobs API — every posting on any Workday career site, with facets, search, posted dates and full descriptions.
• New Job Postings Monitor — new, closed and changed postings on the career sites you watch.
• Hiring Signals API — Open Roles & Hiring Surge by Company — one row per company per run: open roles, what opened and closed, department and seniority breakdowns, and a hiring-surge flag.
• Remote Jobs API — RemoteOK, Remotive, We Work Remotely, Himalayas, Jobicy and more in one schema, deduplicated.
• Shopify Products API — any Shopify store's catalogue, variants, prices and stock signals.
• WooCommerce Products API — any WooCommerce store's catalogue, prices, variants and stock through its public Store API.
• Shopify App Store API — Shopify App Store listings by category, collection or developer: pricing plans, ratings and merchant reviews.
• Shopify Store Monitor — price drops, sales, restocks, sell-outs and new products on any Shopify store, one row per change.
• Public Tenders API — EU TED, UK Find a Tender and Contracts Finder notices by keyword, CPV code, country, stage and deadline.
• Nonprofit & IRS 990 Lookup API — search US nonprofits and get EIN, NTEE code and multi-year Form 990 financials.
• OpenStreetMap Places API — businesses and points of interest by category and area from OpenStreetMap: name, address, coordinates, website, phone, opening hours.

Apps & games

• App Store & Google Play Reviews API — reviews from both stores with ratings, versions and developer replies.
• App Store Top Charts & App Search API — Apple top charts by country and genre, plus app search and details.
• App Store Keyword Rank Tracker — where any app ranks for any keyword on the App Store and Google Play, with rank changes and ASO suggestions.
• Steam Reviews API — Steam reviews with playtime, helpfulness and game details.
• Steam Game Data API — prices, tags, review scores, live player counts and top charts.
• Sports Scores & Schedules API — scores, schedules, standings, teams and headlines for the NFL, NBA, MLB, NHL, soccer and more, no key.
• App Store Monitor — App Store and Google Play listings watched between runs: new versions with release notes, price, rating and listing changes, one row per change.