Luma
Modern event hosting platform with REST APIs for creating events, managing ticketing, tracking attendance, and building community around live and virtual events.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Luma the way a machine reads it — 215 machine-readable artifacts across 6 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Luma scores 51.3/100 (developing), with a separate agent-readiness read of 48/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Luma
Each block below is one kind of artifact we hold for Luma. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 6
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Luma Calendars API
The Calendars API from Luma — 25 operation(s) for calendars.
Luma Events API
The Events API from Luma — 21 operation(s) for events.
Luma Memberships API
The Memberships API from Luma — 3 operation(s) for memberships.
Luma Miscellaneous API
The Miscellaneous API from Luma — 3 operation(s) for miscellaneous.
Luma Organizations API
The Organizations API from Luma — 5 operation(s) for organizations.
Luma Webhooks API
The Webhooks API from Luma — 5 operation(s) for webhooks.
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Plans
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Finops
FINOPSSemantic Vocabularies 2
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Api Context
JSON-LDcontext Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Luma API Rules
SPECTRALJSON Schema 110
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
V1 Calendar Add Event Post 200 Response
JSON SCHEMAV1 Calendar Add Event Post Request
JSON SCHEMAV1 Calendar Admins List Get 200 Response
JSON SCHEMAV1 Calendar Approve Event Post 200 Response
JSON SCHEMAV1 Calendar Approve Event Post Request
JSON SCHEMAV1 Calendar Lookup Event Get 200 Response
JSON SCHEMAV1 Calendar Reject Event Post 200 Response
JSON SCHEMAV1 Calendar Reject Event Post Request
JSON SCHEMAV1 Calendars Contact Tags Apply Post Request
JSON SCHEMAV1 Calendars Contacts Import Post Request
JSON SCHEMAV1 Calendars Contacts List Get 200 Response
JSON SCHEMAV1 Calendars Coupons Create Post Request
JSON SCHEMAV1 Calendars Coupons List Get 200 Response
JSON SCHEMAV1 Calendars Coupons Update Post Request
JSON SCHEMAV1 Calendars Event Tags Apply Post Request
JSON SCHEMAV1 Calendars Event Tags Create Post Request
JSON SCHEMAV1 Calendars Event Tags Delete Post Request
JSON SCHEMAV1 Calendars Event Tags Unapply Post Request
JSON SCHEMAV1 Calendars Event Tags Update Post Request
JSON SCHEMAV1 Calendars Events List Get 200 Response
JSON SCHEMAV1 Calendars Get Get 200 Response
JSON SCHEMAV1 Calendars Update Post 200 Response
JSON SCHEMAV1 Calendars Update Post Request
JSON SCHEMAV1 Entity Lookup Get 200 Response
JSON SCHEMAV1 Events Cancel Post 200 Response
JSON SCHEMAV1 Events Cancel Post Request
JSON SCHEMAV1 Events Cancel Request Post 200 Response
JSON SCHEMAV1 Events Cancel Request Post Request
JSON SCHEMAV1 Events Coupons Create Post 200 Response
JSON SCHEMAV1 Events Coupons Create Post Request
JSON SCHEMAV1 Events Coupons List Get 200 Response
JSON SCHEMAV1 Events Coupons Update Post 200 Response
JSON SCHEMAV1 Events Coupons Update Post Request
JSON SCHEMAV1 Events Create Post 200 Response
JSON SCHEMAV1 Events Create Post Request
JSON SCHEMAV1 Events Get Get 200 Response
JSON SCHEMAV1 Events Guests Add Post 200 Response
JSON SCHEMAV1 Events Guests Add Post Request
JSON SCHEMAV1 Events Guests Get Get 200 Response
JSON SCHEMAV1 Events Guests List Get 200 Response
JSON SCHEMAV1 Events Guests Send Invites Post Request
JSON SCHEMAV1 Events Guests Update Status Post Request
JSON SCHEMAV1 Events Hosts Add Post 200 Response
JSON SCHEMAV1 Events Hosts Add Post Request
JSON SCHEMAV1 Events Hosts Remove Post 200 Response
JSON SCHEMAV1 Events Hosts Remove Post Request
JSON SCHEMAV1 Events Hosts Update Post 200 Response
JSON SCHEMAV1 Events Hosts Update Post Request
JSON SCHEMAV1 Events Ticket Types Create Post Request
JSON SCHEMAV1 Events Ticket Types Delete Post Request
JSON SCHEMAV1 Events Ticket Types Get Get 200 Response
JSON SCHEMAV1 Events Ticket Types List Get 200 Response
JSON SCHEMAV1 Events Ticket Types Update Post Request
JSON SCHEMAV1 Events Update Post 200 Response
JSON SCHEMAV1 Events Update Post Request
JSON SCHEMAV1 Images Create Upload Url Post Request
JSON SCHEMAV1 Memberships Members Add Post 200 Response
JSON SCHEMAV1 Memberships Members Add Post Request
JSON SCHEMAV1 Memberships Tiers List Get 200 Response
JSON SCHEMAV1 Users Get Self Get 200 Response
JSON SCHEMAV1 Webhooks Delete Post 200 Response
JSON SCHEMAV1 Webhooks Delete Post Request
JSON SCHEMAV1 Webhooks List Get 200 Response
JSON SCHEMAV2 Webhooks Create Post 200 Response
JSON SCHEMAV2 Webhooks Create Post Request
JSON SCHEMAV2 Webhooks Get Get 200 Response
JSON SCHEMAV2 Webhooks Update Post 200 Response
JSON SCHEMAV2 Webhooks Update Post Request
JSON SCHEMAWebhook Calendar.Event.Added Post Request
JSON SCHEMAWebhook Event.Canceled Post Request
JSON SCHEMAWebhook Event.Created Post Request
JSON SCHEMAWebhook Event.Updated Post Request
JSON SCHEMAWebhook Guest.Registered Post Request
JSON SCHEMAWebhook Guest.Updated Post Request
JSON SCHEMAWebhook Ticket.Registered Post Request
JSON SCHEMAScroll within the panel for all 110 ·
Examples 89
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Scroll within the panel for all 89 ·
Security Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Luma — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 1
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 1
Pricing, plans, and the legal terms of use
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/luma · machine-readable index on apis.io