Lu.ma is an event management and community platform for creating, hosting, and managing events. Its public API provides programmatic access to events, guest lists, contacts, membership tiers, and related data, and lets you create and update events, manage guests, and import contacts. Nexla connects to the Lu.ma API to ingest event and community data or to push updates back into a Lu.ma calendar.
Power end-to-end data operations for your Lu.ma API with Nexla. Our bi-directional Lu.ma connector is purpose-built for Lu.ma, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Lu.ma or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Lu.ma workflows fast, secure, and fully governed.
Features
Type: API
SourceDestination
Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
Request optimization with intelligent batching, retry, and caching to minimize API calls and costs
Before creating a Lu.ma credential, you need to obtain an API key for the calendar you want to access. Lu.ma API access requires an active Luma Plus subscription on that calendar, and each API key is scoped to a single calendar. Lu.ma uses API key authentication, with the key sent in the x-luma-api-key request header.
To obtain your Lu.ma API key, follow these steps:
Sign in to your Lu.ma account, and go to your calendars from Calendars Home.
Select the calendar you want to access with the API. The calendar must have an active Luma Plus subscription for API access to be available.
Open the calendar's Settings, and select the Developer section.
In the API Keys section, copy the displayed API key.
Store the API key securely, as you will need it to configure your Nexla credential. The API key grants access to the associated calendar's data and should be treated as sensitive information.
The API key is sent in the x-luma-api-key header for all requests to the Lu.ma API. Calendar API keys are rate limited to 200 requests per minute per calendar. If a request is made with a missing or invalid key, the API returns a 401 Unauthorized response. For complete information about API authentication and available endpoints, see the Lu.ma API documentation.
After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
Enter your Lu.ma API key in the API Key field. This is the key you copied from the Developer section of your calendar settings in Prerequisites. The API key is sent in the x-luma-api-key header for all requests and must be kept confidential.
Enter the Lu.ma API base URL in the Base URL field. Unless directed otherwise by Lu.ma, use the default value https://public-api.luma.com/v1.
Each Lu.ma API key is scoped to a single calendar and requires an active Luma Plus subscription. If your API key is compromised, revoke it in the calendar's Developer settings and generate a new one.
For detailed information about API authentication, rate limits, and available endpoints, see the Lu.ma API documentation.
Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.
To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Lu.ma connector tile, then select the credential that will be used to connect to Lu.ma, and click Next; or, create a new Lu.ma credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Lu.ma endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.
[Rest API] List Events
This endpoint template returns a list of events from the calendar. Use this template when you need to access event information for analysis, reporting, or integration purposes.
This endpoint returns events for the calendar associated with your API key. Results are paginated, and Nexla automatically follows the pagination cursor to fetch subsequent pages of data.
For detailed information about the response structure, parameters, and available event data, see the Lu.ma API documentation.
[Rest API] Get Event Guests
This endpoint template returns a list of guests attending a specific event. Use this template when you need to access guest lists, registration details, or attendee data.
This endpoint returns the guests for a specified event. Results are paginated, and Nexla automatically follows the pagination cursor to fetch subsequent pages of data.
For detailed information about the response structure, parameters, and available guest data, see the Lu.ma API documentation.
[Rest API] List Contacts
This endpoint template returns a list of contacts for the calendar. Use this template when you need to access contact information for analysis, reporting, or integration purposes.
This endpoint returns contacts for the calendar associated with your API key. Results are paginated, and Nexla automatically follows the pagination cursor to fetch subsequent pages of data.
For detailed information about the response structure, parameters, and available contact data, see the Lu.ma API documentation.
[Rest API] Get Calendar
This endpoint template returns information about the authenticated user's calendar. Use this template when you need to access calendar metadata and settings.
This endpoint returns details for the calendar associated with your API key as a single record.
For detailed information about the response structure and available calendar data, see the Lu.ma API documentation.
[Rest API] Get Self
This endpoint template returns information about the currently authenticated user. Use this template when you need to access the profile associated with your API key.
This endpoint returns details for the authenticated user as a single record.
For detailed information about the response structure and available user data, see the Lu.ma API documentation.
[Rest API] List Ticket Types
This endpoint template returns a list of ticket types for an event. Use this template when you need to access ticketing configuration and pricing details.
This endpoint returns the ticket types for a specified event. Results are paginated, and Nexla automatically follows the pagination cursor to fetch subsequent pages of data.
For detailed information about the response structure, parameters, and available ticket type data, see the Lu.ma API documentation.
[Rest API] Get Event
This endpoint template returns admin information about an event that you have manage access for. Use this template when you need detailed administrative details for a specific event.
This endpoint returns details for a specified event as a single record.
For detailed information about the response structure, parameters, and available event data, see the Lu.ma API documentation.
[Rest API] Get Guest
This endpoint template returns detailed information for an event guest looked up by their ID. Use this template when you need attendee details for a specific guest.
This endpoint returns details for a specified guest as a single record.
For detailed information about the response structure, parameters, and available guest data, see the Lu.ma API documentation.
[Rest API] List Contact Tags
This endpoint template returns all contact tags for the calendar. Use this template when you need to access the tags used to organize contacts.
This endpoint returns contact tags for the calendar associated with your API key. Results are paginated, and Nexla automatically follows the pagination cursor to fetch subsequent pages of data.
For detailed information about the response structure and available contact tag data, see the Lu.ma API documentation.
[Rest API] List Event Tags
This endpoint template returns all event tags for the calendar. Use this template when you need to access the tags used to organize events.
This endpoint returns event tags for the calendar associated with your API key. Results are paginated, and Nexla automatically follows the pagination cursor to fetch subsequent pages of data.
For detailed information about the response structure and available event tag data, see the Lu.ma API documentation.
[Rest API] List Membership Tiers
This endpoint template returns the available membership tiers for the calendar. Use this template when you need to access membership configuration for a community.
This endpoint returns membership tiers for the calendar associated with your API key. Results are paginated, and Nexla automatically follows the pagination cursor to fetch subsequent pages of data.
For detailed information about the response structure and available membership tier data, see the Lu.ma API documentation.
[Rest API] Lookup Event
This endpoint template checks whether an event already exists on the calendar by looking it up by URL or other identifier. Use this template when you need to resolve an event reference to its Lu.ma record.
This endpoint returns the matching event, if any, as a single record.
For detailed information about the response structure, parameters, and lookup behavior, see the Lu.ma API documentation.
Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.
Lu.ma data sources can also be manually configured to ingest data from any valid Lu.ma API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.
Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Lu.ma data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.
Click the + icon on the Nexset that will be sent to the Lu.ma destination, and select the Send to Destination option from the menu. Select the Lu.ma connector from the list of available destination connectors, then select the credential that will be used to connect to Lu.ma, and click Next; or, create a new Lu.ma credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Lu.ma endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.
[Rest API] Create Event
This endpoint template creates a new event on a calendar using records from a Nexset. Use this template when you need to automatically create Lu.ma events based on data from your Nexla flows.
This endpoint sends data as JSON in the request body. Each record from your Nexset is sent as a separate request to create a new event, and the request body must contain the event data in the format required by the Lu.ma API.
The event structure must match the Lu.ma API's expected format. For detailed information about event creation, request body formats, and available event properties, see the Lu.ma API documentation.
[Rest API] Update Event
This endpoint template updates attributes on an existing event using records from a Nexset. Use this template when you need to keep Lu.ma events in sync with data from your Nexla flows.
This endpoint sends data as JSON in the request body. Each record from your Nexset is sent as a separate request, and the request body must identify the target event and contain the attributes to update.
The request structure must match the Lu.ma API's expected format. For detailed information about event updates, request body formats, and available event properties, see the Lu.ma API documentation.
[Rest API] Add Guest to Event
This endpoint template adds a guest (attendee) to an event using records from a Nexset. Use this template when you need to register individual guests to a Lu.ma event.
This endpoint sends data as JSON in the request body. Each record from your Nexset is sent as a separate request to add a guest, and the request body must identify the target event and the guest to add.
The request structure must match the Lu.ma API's expected format. For detailed information about adding guests, request body formats, and available guest properties, see the Lu.ma API documentation.
[Rest API] Add Guests
This endpoint template adds guests to an event using records from a Nexset. Use this template when you need to register attendees to a Lu.ma event.
This endpoint sends data as JSON in the request body. Each record from your Nexset is sent as a separate request, and the request body must identify the target event and the guests to add.
The request structure must match the Lu.ma API's expected format. For detailed information about adding guests, request body formats, and available guest properties, see the Lu.ma API documentation.
[Rest API] Update Guest Status
This endpoint template updates a guest's registration status for an event using records from a Nexset. Use this template when you need to change the approval or attendance status of guests.
This endpoint sends data as JSON in the request body. Each record from your Nexset is sent as a separate request, and the request body must identify the target guest and the new status.
The request structure must match the Lu.ma API's expected format. For detailed information about guest status updates and request body formats, see the Lu.ma API documentation.
[Rest API] Import Contacts
This endpoint template imports contacts to your calendar using records from a Nexset, making it easy to invite them to events. Use this template when you need to populate your Lu.ma calendar's contact list from your Nexla flows.
This endpoint sends data as JSON in the request body. Each record from your Nexset is sent as a separate request, and the request body must contain the contact data in the format required by the Lu.ma API.
The request structure must match the Lu.ma API's expected format. For detailed information about importing contacts and request body formats, see the Lu.ma API documentation.
[Rest API] Delete Event
This endpoint template deletes an existing event from the calendar using records from a Nexset. Use this template when you need to remove Lu.ma events based on data from your Nexla flows.
This endpoint sends data as JSON in the request body. Each record from your Nexset is sent as a separate request, and the request body must identify the event to delete.
Deleting an event is not reversible. The request structure must match the Lu.ma API's expected format. For detailed information about event deletion and request body formats, see the Lu.ma API documentation.
[Rest API] Cancel Event
This endpoint template cancels an event using a cancellation token, sourced from records in a Nexset. Use this template when you need to cancel Lu.ma events based on data from your Nexla flows.
This endpoint sends data as JSON in the request body. Each record from your Nexset is sent as a separate request, and the request body must include the cancellation token for the event.
The request structure must match the Lu.ma API's expected format. For detailed information about event cancellation and request body formats, see the Lu.ma API documentation.
Lu.ma destinations can also be manually configured to send data to any valid Lu.ma API endpoint. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.
Lu.ma APIs expect JSON format for write operations. Ensure each record includes the identifiers and fields required by the target endpoint.
Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured Lu.ma endpoint, open the destination resource menu, and select Activate.
The Nexset data will not be sent to the Lu.ma endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.
