How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Luma Events API

The Events API from Luma — 21 operation(s) for events.

Luma Events API is one of 7 APIs that Luma publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Event. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, authentication docs, and rate-limit docs.

This API exposes 21 operations across 21 paths. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against a single base URL, https://public-api.luma.com.

21 operations 21 paths 0 schemas 6 GET15 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://public-api.luma.com
Authentication
API Key
License
Proprietary
Resource Areas
1

Authentication & Security 1

Luma Events API declares 1 security scheme for authenticating requests. An API key is passed in the header as x-luma-api-key (apiKeyAuth). By default, every request must be authenticated.

  • apiKeyAuth — API key to authenticate requests to the Luma API. Generate an API key on your Luma dashboard.

Paths & Operations 21

Across 21 paths, the API surfaces 21 operations — 6 GET, 15 POST. Each is listed below with its method, path, parameters, and response codes.

Events 21
GET
/v1/events/get
Get Event
1 param → 200
GET
/v1/events/guests/get
Get Guest
2 params → 200
GET
/v1/events/guests/list
List Guests
6 params → 200
GET
/v1/events/coupons/list
List Event Coupons
3 params → 200
GET
/v1/events/ticket-types/list
List Ticket Types
2 params → 200
GET
/v1/events/ticket-types/get
Get Ticket Type
1 param → 200
POST
/v1/events/create
Create Event
body → 200
POST
/v1/events/update
Update Event
body → 200
POST
/v1/events/guests/update-status
Update Guest Status
body → 200
POST
/v1/events/guests/send-invites
Send Invites
body → 200
POST
/v1/events/guests/add
Add Guests
body → 200
POST
/v1/events/hosts/add
Add Host
body → 200
POST
/v1/events/hosts/update
Update Host
body → 200
POST
/v1/events/hosts/remove
Remove Host
body → 200
POST
/v1/events/coupons/create
Create Coupon
body → 200
POST
/v1/events/coupons/update
Update Coupon
body → 200
POST
/v1/events/ticket-types/create
Create Ticket Type
body → 200
POST
/v1/events/ticket-types/update
Update Ticket Type
body → 200
POST
/v1/events/ticket-types/delete
Delete Ticket Type
body → 200
POST
/v1/events/cancel/request
Request Event Cancellation
body → 200
POST
/v1/events/cancel
Cancel Event
body → 200

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

luma-events-api-openapi.yml Raw ↑

Other APIs Luma publishes across the network.

Luma Calendars API
Luma Memberships API
Luma Miscellaneous API
Luma Organizations API
Luma Webhooks API
Luma Webhook Types API
Where this information came from

This is an independent, third-party profile of Luma Events API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.