luma
Luma event platform API for managing events, guests, tickets, and calendar data. Use when user mentions "Luma", "lu.ma", "event", "ticket", "guest list", "RSVP", or "calendar event".
What this skill does
## Troubleshooting
If requests fail, run `zero doctor check-connector --env-name LUMA_API_KEY` or `zero doctor check-connector --url https://public-api.luma.com/v1/user/get-self --method GET`
## Authentication
All requests require an API key passed in the header:
```
x-luma-api-key: $LUMA_API_KEY
```
Get your API key from: Luma → Calendars Home → select calendar → Settings → Developer → API Keys.
> A Luma Plus subscription is required for API access. Each API key is scoped to a single calendar.
## Rate Limits
- Calendar API keys: 200 requests/min
- Organization API keys: 500 requests/min
## Key Endpoints
Base URL: `https://public-api.luma.com`
### Events
**Get Event**
`GET /v1/event/get?id=evt-...`
Returns admin information about an event you have manage access for.
```bash
curl -s "https://public-api.luma.com/v1/event/get?id=$EVENT_ID" \
-H "x-luma-api-key: $LUMA_API_KEY"
```
**List Calendar Events**
`GET /v1/calendar/list-events`
List all events managed by the calendar. Supports pagination, date filtering, and status.
```bash
curl -s "https://public-api.luma.com/v1/calendar/list-events?pagination_limit=25" \
-H "x-luma-api-key: $LUMA_API_KEY"
```
Parameters:
- `before` / `after` — ISO 8601 datetime filter
- `pagination_cursor` — cursor from previous response `next_cursor`
- `pagination_limit` — results per page
- `status` — `approved` (default) or `pending`
### Guests
**Get Guest**
`GET /v1/event/get-guest?event_id=evt-...&id=gst-...`
Look up a guest by guest ID, ticket key, guest key, or email.
```bash
curl -s "https://public-api.luma.com/v1/event/get-guest?event_id=$EVENT_ID&id=$GUEST_ID" \
-H "x-luma-api-key: $LUMA_API_KEY"
```
**List Guests**
`GET /v1/event/get-guests?event_id=evt-...`
Paginated list of guests registered or invited to an event.
```bash
curl -s "https://public-api.luma.com/v1/event/get-guests?event_id=$EVENT_ID&pagination_limit=50" \
-H "x-luma-api-key: $LUMA_API_KEY"
```
Parameters:
- `approval_status` — filter: `approved`, `session`, `pending_approval`, `invited`, `declined`, `waitlist`
- `sort_column` — `name`, `email`, `created_at`, `registered_at`, `checked_in_at`
- `sort_direction` — `asc`, `desc`
### Calendar
**Get Calendar**
`GET /v1/calendar/get`
Returns calendar info: name, slug, description, location, social handles.
```bash
curl -s "https://public-api.luma.com/v1/calendar/get" \
-H "x-luma-api-key: $LUMA_API_KEY"
```
**List People**
`GET /v1/calendar/list-people`
Search and filter people associated with the calendar.
```bash
curl -s "https://public-api.luma.com/v1/calendar/list-people?pagination_limit=25" \
-H "x-luma-api-key: $LUMA_API_KEY"
```
Parameters:
- `query` — search over names and emails
- `member_status` — `approved`, `pending`, `approved-pending-payment`, `declined`
- `sort_column` — `created_at`, `event_checked_in_count`, `event_approved_count`, `name`, `revenue_usd_cents`
**List Admins**
`GET /v1/calendar/admins/list`
```bash
curl -s "https://public-api.luma.com/v1/calendar/admins/list" \
-H "x-luma-api-key: $LUMA_API_KEY"
```
### Tickets
**List Ticket Types**
`GET /v1/event/ticket-types/list?event_id=evt-...`
```bash
curl -s "https://public-api.luma.com/v1/event/ticket-types/list?event_id=$EVENT_ID" \
-H "x-luma-api-key: $LUMA_API_KEY"
```
### Coupons
**List Event Coupons**
`GET /v1/event/coupons?event_id=evt-...`
```bash
curl -s "https://public-api.luma.com/v1/event/coupons?event_id=$EVENT_ID" \
-H "x-luma-api-key: $LUMA_API_KEY"
```
**List Calendar Coupons**
`GET /v1/calendar/coupons`
```bash
curl -s "https://public-api.luma.com/v1/calendar/coupons" \
-H "x-luma-api-key: $LUMA_API_KEY"
```
### User
**Get Current User**
`GET /v1/user/get-self`
Test authentication and get the authenticated user's info.
```bash
curl -s "https://public-api.luma.com/v1/user/get-self" \
-H "x-luma-api-key: $LUMA_API_KEY"
```
### Lookup
**Lookup Entity by Slug**
`GET /v1/entity/lookup?slug=...`
Resolve a calendar or event by its slug.
```bash
curl -s "https://public-api.luma.com/v1/entity/lookup?slug=$SLUG" \
-H "x-luma-api-key: $LUMA_API_KEY"
```
## Common Workflows
### Check Upcoming Events
```bash
curl -s "https://public-api.luma.com/v1/calendar/list-events?pagination_limit=10" \
-H "x-luma-api-key: $LUMA_API_KEY" | jq '.entries[] | {name: .event.name, start: .event.start_at, url: .event.url}'
```
### Get Guest List for an Event
```bash
curl -s "https://public-api.luma.com/v1/event/get-guests?event_id=$EVENT_ID&pagination_limit=50" \
-H "x-luma-api-key: $LUMA_API_KEY" | jq '.entries[] | {name: .user_name, email: .user_email, status: .approval_status}'
```
### Find a Person by Email
```bash
curl -s "https://public-api.luma.com/v1/calendar/list-people?query=$EMAIL&pagination_limit=5" \
-H "x-luma-api-key: $LUMA_API_KEY" | jq '.entries[] | {name: .user.name, email: .email, events: .event_approved_count}'
```
## Notes
- All list endpoints use cursor-based pagination: pass `pagination_cursor` from the prior response's `next_cursor`
- All datetime fields use ISO 8601 format
- The `api_id` parameter is deprecated across all endpoints; use `id` instead
- Event IDs start with `evt-`, guest IDs with `gst-`, ticket type IDs with `ett-`
- Full OpenAPI spec available at `https://public-api.luma.com/openapi.json`
Related in Backend & APIs
jfrog
IncludedInteract with the JFrog Platform via the JFrog CLI and REST/GraphQL APIs. Use this skill when the user wants to manage Artifactory repositories, upload or download artifacts, manage builds, configure permissions, manage users and groups, work with access tokens, configure JFrog CLI servers, search artifacts, manage properties, set up replication, manage JFrog Projects, run security audits or scans, look up CVE details, query exposures scan results from JFrog Advanced Security, manage release bundles and lifecycle operations, aggregate or export platform data, or perform any JFrog Platform administration task. Also use when the user mentions jf, jfrog, artifactory, xray, distribution, evidence, apptrust, onemodel, graphql, workers, mission control, curation, advanced security, exposures, or any JFrog product name.
cupynumeric-migration-readiness
IncludedPre-migration readiness assessor for porting NumPy to cuPyNumeric. Use BEFORE substantial porting work begins when the user asks whether code will scale on GPU, whether they should migrate to cuPyNumeric, which NumPy patterns transfer cleanly, what must be refactored before porting, or mentions pre-port assessment, scaling analysis, or refactor planning. Inspect the user's source code, look up NumPy usage, cross-reference the cuPyNumeric API support manifest, and distinguish distributed-scaling-friendly patterns from blockers such as unsupported APIs, scalar synchronization, host round-trips, Python/object-heavy control flow, shape/data-dependent branching, and in-place mutation hazards. Produce a verdict of READY, LIGHT REFACTOR, SIGNIFICANT REFACTOR, or NOT RECOMMENDED, with concrete refactor pointers.
alibabacloud-data-agent-skill
IncludedInvoke Alibaba Cloud Apsara Data Agent for Analytics via CLI to perform natural language-driven data analysis on enterprise databases. Data Agent for Analytics is an intelligent data analysis agent developed by Alibaba Cloud Database team for enterprise users. It automatically completes requirement analysis, data understanding, analysis insights, and report generation based on natural language descriptions. This tool supports: discovering data resources (instances/databases/tables) managed in DMS, initiating query or deep analysis sessions, real-time progress tracking, and retrieving analysis conclusions and generated reports. Use this Skill when users need to query databases, analyze data trends, generate data reports, ask questions in natural language, or mention "Data Agent", "data analysis", "database query", "SQL analysis", "data insights".
token-optimizer
IncludedReduce OpenClaw token usage and API costs through smart model routing, heartbeat optimization, budget tracking, and native 2026.2.15 features (session pruning, bootstrap size limits, cache TTL alignment). Use when token costs are high, API rate limits are being hit, or hosting multiple agents at scale. The 4 executable scripts (context_optimizer, model_router, heartbeat_optimizer, token_tracker) are local-only — no network requests, no subprocess calls, no system modifications. Reference files (PROVIDERS.md, config-patches.json) document optional multi-provider strategies that require external API keys and network access if you choose to use them. See SECURITY.md for full breakdown.
resend-cli
IncludedUse this skill when the task is specifically about operating Resend from an AI agent, terminal session, or CI job via the official resend CLI: installing/authenticating the CLI, sending/listing/updating/cancelling emails, batch sends, domains and DNS, webhooks and local listeners, inbound receiving, contacts, topics, segments, broadcasts, templates, API keys, profiles, or debugging Resend CLI/API failures. Trigger on mentions of Resend CLI, `resend`, `resend doctor`, `resend emails send`, `resend domains`, `resend webhooks listen`, `resend emails receiving`, or agent-friendly terminal automation.
alibabacloud-odps-maxframe-coding
IncludedUse this skill for MaxFrame SDK development and documentation navigation on Alibaba Cloud MaxCompute (ODPS). Helps answer MaxFrame API, concept, official example, and supported pandas API questions; create data processing programs; read/write MaxCompute tables; debug jobs (remote or local); and build custom DPE runtime images. Trigger when users mention MaxFrame, MaxCompute with MaxFrame, ODPS table processing, DPE runtime, MaxFrame docs/examples, DataFrame/Tensor operations, or GPU runtime setup. Works for both English and Chinese queries about Alibaba Cloud data processing with MaxFrame.