Luma API

Name: Luma API
Brand: Luma API
Availability: InStock

✓ Official Vendor SpecProductivityCalendar SchedulingapiKey55 EndpointsREST

For Agents

List events on a Luma calendar, look up guests and ticket types, manage coupons and person tags, and orchestrate event RSVPs.

Install Jentic One Beta

Connect the Luma API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Luma API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Luma API.

List events on a calendar with filters and pagination via /v1/calendar/list-events

Retrieve a single event with /v1/event/get and look up specific guests or the full guest list

Manage ticket types and event coupons including listing, creating, and querying coupon usage

GET STARTED

Start building with Luma API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Luma API for, with concrete tasks.

★ Sync Luma events into a CRM or BI tool

Marketing and growth teams pipe Luma events and guest lists into HubSpot, Salesforce, or a warehouse to attribute leads back to the events they attended. /v1/calendar/list-events pulls the event roster, /v1/event/get-guests pulls the guest list per event, and /v1/calendar/list-person-tags pulls segmentation tags. The result is event-level attendance plus tags ready for downstream segmentation.

Call /v1/calendar/list-events for the next 30 days, then for each event call /v1/event/get-guests and write the guest emails plus ticket type to the CRM.

Coupon and ticket-type management for promo campaigns

Event organisers running promo campaigns need to list and create coupons across a calendar or against a specific event, and confirm which ticket types are available. /v1/calendar/coupons and /v1/event/coupons cover coupon listing at both scopes, while /v1/event/ticket-types/list returns the currently configured ticket types for an event. Operations teams use this to keep coupon codes in sync with email and social campaigns.

List the active coupons on calendar 'cal-xyz' via /v1/calendar/coupons and return the codes plus their remaining redemptions.

Resolve Luma URLs into structured event data

Tools that ingest event URLs from emails or chat need to resolve them into structured Luma data without scraping. /v1/entity/lookup and /v1/calendar/lookup-event take an identifier or URL and return the underlying calendar or event entity. This lets a chatbot or agent answer 'what's on this event link?' with first-party data.

Pass a Luma event URL to /v1/calendar/lookup-event and return the structured event title, time, and location.

Agent-driven event check-ins via Jentic

An AI assistant for an event organiser is asked 'who is coming tomorrow and have they paid?'. Jentic stores the x-luma-api-key in MAXsystem and exposes the Luma operations by intent so the agent can chain list-events, get-guests, and ticket-types without holding the raw key.

Search Jentic for 'list luma upcoming events', execute it for the next 24 hours, then chain /v1/event/get-guests for each event.

Key Endpoints

55 endpoints — the luma api exposes luma's events platform — calendars, events, guests, ticket types, coupons, person tags, and admin operations.

METHOD

PATH

DESCRIPTION

GET

/v1/calendar/list-events

List events on a calendar

GET

/v1/event/get

Get a single event by ID

GET

/v1/event/get-guests

Get the full guest list for an event

GET

/v1/event/get-guest

Get a specific guest on an event

GET

/v1/event/ticket-types/list

List ticket types configured for an event

GET

/v1/calendar/coupons

List coupons on a calendar

GET

/v1/entity/lookup

Resolve a Luma URL or identifier to its entity

GET

/v1/calendar/list-events

List events on a calendar

GET

/v1/event/get

Get a single event by ID

GET

/v1/event/get-guests

Get the full guest list for an event

GET

/v1/event/get-guest

Get a specific guest on an event

GET

/v1/event/ticket-types/list

List ticket types configured for an event

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The Luma x-luma-api-key is held encrypted in the Jentic MAXsystem vault. Jentic injects it as the x-luma-api-key header on every request to public-api.luma.com, so the raw key never enters the agent's prompt or logs.

Intent-based discovery

Agents search by intent such as 'list luma upcoming events' or 'get event guest list', and Jentic returns the matching Luma operation with its parameter schema for direct execution.

Time to first call

Direct Luma integration: 1-2 days to wire authentication, model the calendar/event/guest hierarchy, and handle pagination. Through Jentic: under 1 hour — search, load schema, execute.

FAQs

Specific to using Luma API through Jentic.

What authentication does the Luma API use?

The Luma API uses an x-luma-api-key header. Generate the key from your Luma dashboard and send it on every request to public-api.luma.com. Through Jentic, the key is stored encrypted in MAXsystem and injected per request — the agent never sees the raw key.

Can I list all upcoming events on a calendar with the Luma API?

Yes. Call GET /v1/calendar/list-events with the calendar identifier and a time range. For a single event by ID use GET /v1/event/get, and for resolving an event URL use /v1/calendar/lookup-event.

What are the rate limits for the Luma API?

Specific rate limits are not declared in the OpenAPI spec. Expect per-account fair-use limits — design clients to retry on 429 responses and avoid full-calendar guest list polling more often than once per minute per event.

How do I pull an event's guest list through Jentic?

Search Jentic for 'luma event guests', load GET /v1/event/get-guests, and execute it with the event ID. The x-luma-api-key is injected automatically and the response gives you the guest emails, RSVP state, and ticket type.

Does the Luma API support creating events programmatically?

The 55 endpoints in this spec focus on read access to events, calendars, guests, tags, ticket types, and coupons. If you need to create an event itself, do so in the Luma dashboard and use this API to read and integrate it into downstream tools.