# Luma Events Lookup: Events, Hosts and Guest Counts (`accountable_eel/luma-events-lookup`) Actor

Extract public events, hosts, guest counts, ticketing, and venues from Luma (lu.ma). Search by city, discover feed, or event URL. Misses are free.

- **URL**: https://apify.com/accountable_eel/luma-events-lookup.md
- **Developed by:** [Adriana Voss](https://apify.com/accountable_eel) (community)
- **Categories:** Lead generation, Marketing
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.25 / 1,000 event returneds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Luma Events Lookup: Events, Hosts and Guest Counts

**Extract public events, hosts, guest counts, ticketing details, and venues from Luma (lu.ma).**

Community managers, event marketers, and recruiters use this actor to monitor tech meetups, demo days, hackathons, and conferences across any city or directly from the Luma discover feed. Retrieve organizer details, venue addresses with coordinates, ticket pricing, and attendee counts without browser overhead. You pay only for events actually returned; misses and empty queries are free.

### How to use

1. **In the Apify Console.** Open the actor page and click **Start** — the `queries` field is already pre-filled with a working example. Results land in the run's dataset as soon as each item is found.
2. **Via the API.** Call it directly with a POST request — no Console needed once you have an API token:
   ```bash
   curl "https://api.apify.com/v2/acts/accountable_eel~luma-events-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
     -X POST \
     -H "Content-Type: application/json" \
     -d '{"queries":["discover"]}'
   ```
3. **On a schedule.** Save this actor as an Apify **Task** with the input you want, then add a **Schedule** (hourly, daily, weekly) so it runs on its own — no server of your own required.

### Input

```json
{
  "queries": [
    "discover"
  ]
}
```

One per line. Enter "discover" for upcoming global events, a city handle (e.g. "sf", "budapest", "london", "nyc"), or a direct event URL (e.g. "https://lu.ma/fundraisingcee"). Accepted formats: discover, san-francisco, budapest, https://lu.ma/fundraisingcee.

You can search worldwide or scope results to a specific city. The actor pages through results automatically up to your `maxItems` cap.

### Output

One row per event, for example:

| query | found | status | searchQuery | eventCount | hasMore | events | eventId | name | eventUrl | startAt | endAt | timezone | locationType | city | country | countryCode | venueAddress | fullAddress | latitude | longitude | calendarName | calendarUrl | primaryHost | hostNames | guestCount | ticketCount | isFree | isSoldOut | price | priceCents | currency | spotsRemaining | coverUrl | eventType | sourceUrl | scrapedAt |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| discover | true | OK | <query or source searched> | <events returned> | <more events available> | \<all events found (full list)> | <event id> | <event name> | <event url> | <start time> | <end time> | <timezone> | \<location type (offline/online)> | <city> | <country> | <country code> | \<venue / address> | <full address> | <latitude> | <longitude> | \<calendar / host organisation> | <calendar url> | <primary host name> | <all host names> | <guest count> | <ticket count> | \<free event?> | \<sold out?> | <ticket price text> | <price in cents> | <currency> | <spots remaining> | <cover image url> | <event type> | <source url> | 1970-01-01T00:00:00.000Z |

A miss comes back as a row with `"found": false` and is never charged. Missing fields are `null`, never `0` or empty strings.

### Pricing

- **Event returned**: $2.50 per 1,000 events

Plus a $0.002 start fee per run. Charged per event returned — misses (`found:false`) are free.

### Example runs

Paste any of these into the Input tab and press Start. All three run keyless with no login or setup required.

**Upcoming featured events from the Discover feed (default).**

```json
{
  "queries": ["discover"],
  "maxItems": 20
}
```

**Tech and community events in San Francisco.**

```json
{
  "queries": ["sf"],
  "maxItems": 30
}
```

**Free public events in Budapest.**

```json
{
  "queries": ["budapest"],
  "freeOnly": true,
  "maxItems": 20
}
```

### Use it from Clay, n8n, Make, or an AI agent

This actor runs synchronously over plain HTTP — call it directly from a script, a workflow tool, or an AI agent, no Apify Console needed once you have an API token.

```bash
curl "https://api.apify.com/v2/acts/accountable_eel~luma-events-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
  -X POST \
  -H "Content-Type: application/json" \
  -d '{"queries":["discover"]}'
```

**n8n.** Add an HTTP Request node: Method `POST`, URL `https://api.apify.com/v2/acts/accountable_eel~luma-events-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>`, Body Content Type `JSON`, JSON Body `{"queries":["discover"]}` (swap in an expression from an earlier node for a real value).

**Clay.** Add an "HTTP API" column: Method `POST`, URL `https://api.apify.com/v2/acts/accountable_eel~luma-events-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>`, Body `{"queries":["{{query}}"]}`, mapping the row's query into the `queries` array.

**MCP.** In Claude, Cursor, or any MCP client with the Apify MCP server, ask for "luma events scraper" — the agent will find and run this actor.

# Actor input Schema

## `queries` (type: `array`):

One per line. Enter "discover" for upcoming global events, a city handle (e.g. "sf", "budapest", "london", "nyc"), or a direct event URL (e.g. "https://lu.ma/fundraisingcee"). Accepted formats: discover, san-francisco, budapest, https://lu.ma/fundraisingcee. You're only charged for the ones we actually find — a miss costs nothing.

## `mode` (type: `string`):

Pick the option that matches what you need — you can leave this on the recommended setting.

## `testRun` (type: `boolean`):

Turn this on to test your input on a small sample before running the full list. Turn it off to process everything.

## `onlyFound` (type: `boolean`):

Only keep rows where something was actually found. Misses are always free, whether or not you show them here.

## `includeKeywords` (type: `array`):

Optional. Only keep results that mention at least one of these words (e.g. a job title, a city, a product name). Leave empty to keep everything.

## `excludeKeywords` (type: `array`):

Optional. Drop any result that mentions one of these words. Leave empty to skip nothing.

## `maxResults` (type: `integer`):

Optional. Stop the run once this many results have been found — useful for a quick, cheap sample. Leave blank for no limit.

## `maxItems` (type: `integer`):

Cap on total event rows returned per query / discover feed. Default 20.

## `city` (type: `string`):

Optional city name or handle (e.g. "Budapest", "sf", "New York", "London"). Leave empty for worldwide.

## `freeOnly` (type: `boolean`):

When enabled, returns only events that are free to attend.

## `columns` (type: `array`):

Choose which pieces of information to include in each result row. All are included by default.

## `expandRows` (type: `boolean`):

When on, each event found gets its own row instead of being grouped under its query. You're still only charged once per query, no matter how many rows it produces.

## `maxConcurrency` (type: `integer`):

Parallel requests. Keep conservative — this target has no browser fallback, so getting blocked costs more than slow-and-steady.

## `proxyConfiguration` (type: `object`):

Apify Proxy config. Residential recommended for anti-bot-sensitive targets.

## Actor input object example

```json
{
  "queries": [
    "discover"
  ],
  "mode": "discover",
  "testRun": false,
  "onlyFound": false,
  "includeKeywords": [],
  "excludeKeywords": [],
  "maxItems": 20,
  "city": "",
  "freeOnly": false,
  "columns": [
    "searchQuery",
    "eventCount",
    "hasMore",
    "events",
    "eventId",
    "name",
    "eventUrl",
    "startAt",
    "endAt",
    "timezone",
    "locationType",
    "city",
    "country",
    "countryCode",
    "venueAddress",
    "fullAddress",
    "latitude",
    "longitude",
    "calendarName",
    "calendarUrl",
    "primaryHost",
    "hostNames",
    "guestCount",
    "ticketCount",
    "isFree",
    "isSoldOut",
    "price",
    "priceCents",
    "currency",
    "spotsRemaining",
    "coverUrl",
    "eventType",
    "sourceUrl"
  ],
  "expandRows": true,
  "maxConcurrency": 5,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "queries": [
        "discover"
    ],
    "includeKeywords": [],
    "excludeKeywords": []
};

// Run the Actor and wait for it to finish
const run = await client.actor("accountable_eel/luma-events-lookup").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "queries": ["discover"],
    "includeKeywords": [],
    "excludeKeywords": [],
}

# Run the Actor and wait for it to finish
run = client.actor("accountable_eel/luma-events-lookup").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "queries": [
    "discover"
  ],
  "includeKeywords": [],
  "excludeKeywords": []
}' |
apify call accountable_eel/luma-events-lookup --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,accountable_eel/luma-events-lookup"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/nqYYXXK0OWRsIITBU/builds/WrLN3c8W1EBGqHNSj/openapi.json