Be the first to get access to new connectors. Get early access →
ConnectorBay Early access

Luma (BYOK) — connector documentation

  • MCP endpoint: https://byok-luma.connectorbay.com/mcp
  • REST API: POST https://byok-luma.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-luma.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own Luma calendar API key (one key per calendar; the API needs a Luma Plus subscription), sent in the X-Upstream-Key header of every request (never stored, logged or cached)
  • Health: https://byok-luma.connectorbay.com/health · Tool schemas: https://byok-luma.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-luma · agent@connectorbay.com

What Luma (BYOK) is for

Luma (BYOK) lets an AI assistant read your own Luma data through the Luma API with a key you supply (calendar API key (one key per calendar; the API needs a Luma Plus subscription)). Read-only: 11 tools (get_calendar, list_calendar_events, get_event, list_event_guests, list_event_ticket_types, list_event_coupons, list_event_blasts, list_calendar_contacts, list_calendar_admins, list_event_tags, list_membership_tiers). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to public-api.luma.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Luma. Luma and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

  • "Which Luma calendar is my API key for?"
  • "What events are coming up on my Luma calendar?"
  • "Show the details of Luma event evt-abc123"
  • "Who has registered for Luma event evt-abc123?"
  • "What ticket types does Luma event evt-abc123 have?"
  • "Which coupon codes exist for Luma event evt-abc123?"

What it does

  • get_calendar: Show the calendar the API key belongs to: name, slug, URL, description, location, social handles and default event settings.
  • list_calendar_events: List the events of the calendar with name, start and end time, time zone and URL. By default only events the calendar manages and that are approved.
  • get_event: Get one event: name, start and end time, time zone, URL, visibility, location type, registration state, approval requirement, remaining spots and hosts.
  • list_event_guests: List the guests who registered for or were invited to an event with name, email, approval status and registration time. Contains personal data.
  • list_event_ticket_types: List an event's ticket types with name, free or paid, price in cents, currency, capacity, validity window and hidden flag.
  • list_event_coupons: List the coupons created for an event with code, remaining uses, validity, percent or cents off and ticket type.
  • list_event_blasts: List the emails (blasts) sent or scheduled to an event's guests with subject, status, scheduled and sent time, recipient count and open count.
  • list_calendar_contacts: List the calendar's contacts (audience) with name, email, tags, events attended and revenue. Search by name or email. Contains personal data.
  • list_calendar_admins: List the admins of the calendar with name and email.
  • list_event_tags: List the tags available for events on the calendar with name and color.
  • list_membership_tiers: List the calendar's membership tiers, including hidden ones, with name, description, hidden flag and approval requirement.

BYOK key

You bring your own Luma calendar API key (one key per calendar; the API needs a Luma Plus subscription) (https://luma.com/calendar/manage/api-keys). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to public-api.luma.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

Live from the Luma API (public-api.luma.com) with a BYOK key; documentation: https://docs.luma.com/reference/getting-started-with-your-api. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Luma. Luma and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Luma account.

Built for: Worldwide. Languages: English.