# Luma City Upcoming Event Calendar Triage (`jpmarketdata/luma-city-upcoming-event-shortlist`) Actor

Triage the first 20 public upcoming Luma city events per selected city by date, registration availability, free/paid status and listed ticket price. Get source-ranked URLs and explicit coverage limits.

- **URL**: https://apify.com/jpmarketdata/luma-city-upcoming-event-shortlist.md
- **Developed by:** [h ichi](https://apify.com/jpmarketdata) (community)
- **Categories:** Automation, Marketing, Travel
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$0.05 / 1,000 upcoming event shortlisteds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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 City Upcoming Event Calendar Triage

Screen upcoming public events across selected Luma cities for an attendance opportunity calendar. The compact rows show the source event URL, title, normalized schedule, registration availability, ticket cost status and public aggregate guest count, so an operator can find feasible events before opening details.

### Scope

This Actor returns only the first 20 public events embedded in each Luma city page, in source order. It is not an exhaustive city event census, historical archive, sponsorship-fit report, ticket inventory or attendee list. The source city count is shown when more events exist.

### Input

Choose one to three Luma city slugs such as `tokyo`, `london` and `seattle`; default Tokyo and London, including an empty input object. Choose 1–20 rows per city; default 20. Invalid slugs and empty city pages fail clearly.

### Output

One row per complete source event. Rows include city, source rank, public event ID/name/URL, UTC start/end, source timezone, raw registration availability, source free/paid flag, ticket cost status (`free`, `listed-price`, `unknown`), optional listed price cents/currency and public aggregate guest count. A paid event without a listed price keeps `isFree=false` and uses cost status `unknown`, not a zero price; source guest count 0 is not a claim that nobody registered. No full descriptions, addresses, host or attendee profiles, contact details or images.

### Pricing

$0.00005 per delivered `event-shortlisted` row, no start or secondary event; maximum 60 charged rows ($0.003) per run. Failed or undelivered rows are not charged.

### Limits

At most one robots GET and three city HTML GETs, at least three seconds apart, 2 MiB per response, 20-second request timeout, 90-second run timeout and 256 MB. No browser, proxy, token, paid API or private Luma endpoint. Runtime checks robots and fails if access changes. Luma does not endorse this Actor.

### Privacy

Public Luma city/event metadata only. The Actor omits guest and host identity, contacts, addresses, coordinates, images, descriptions and source response bodies. Event titles may contain public person names chosen by organizers; no person enrichment is performed.

# Actor input Schema

## `cities` (type: `array`):

One to three public Luma city slugs from luma.com/{slug}; examples: tokyo, london, seattle. The source's first 20 upcoming city discovery events are available, not a complete city listing.

## `maxEventsPerCity` (type: `integer`):

Return 1–20 first-page source events per city, in source order. This is a discovery shortlist and may omit other city events.

## Actor input object example

```json
{
  "cities": [
    "tokyo",
    "london"
  ],
  "maxEventsPerCity": 20
}
```

# 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 = {
    "cities": [
        "tokyo",
        "london"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("jpmarketdata/luma-city-upcoming-event-shortlist").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 = { "cities": [
        "tokyo",
        "london",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("jpmarketdata/luma-city-upcoming-event-shortlist").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 '{
  "cities": [
    "tokyo",
    "london"
  ]
}' |
apify call jpmarketdata/luma-city-upcoming-event-shortlist --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,jpmarketdata/luma-city-upcoming-event-shortlist"
        }
    }
}
```

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/wMHqs1qldBxnN8FA4/builds/Cf2KjYlaX8p5CkrDr/openapi.json