Luma (v2)
Integrate your application with the Luma API
Quickstart
Connect to Luma with Tenklo and see data flow in 2 minutes. The Luma API uses API key authentication, so no user redirect is required.
In Tenklo (free signup), go to Integrations -> Configure New Integration -> Luma (v2).
Go to Connections -> Add Test Connection. Enter your Luma API key, then save.
Let's make your first request to the Luma API: fetch the user the API key belongs to. Replace the placeholders below with your Environment API key, integration ID, and connection ID:
curl "https://api.tenklo.dev/proxy/v1/users/get-self" \
-H "Authorization: Bearer <NANGO-API-KEY>" \
-H "Provider-Config-Key: <INTEGRATION-ID>" \
-H "Connection-Id: <CONNECTION-ID>"Or fetch credentials with the Node SDK or API.
You're connected! Check the Logs tab in Tenklo to inspect requests.
Follow our Auth implementation guide to integrate Tenklo in your app.
To obtain your own production credentials, follow the setup guide linked below.
Luma integration guides
Tenklo maintained guides for common use cases.
- How to get your Luma API key Create an API key in your Luma calendar settings and connect it to Tenklo
Official docs: Luma API docs
Common scopes
Luma does not use scopes. An API key grants full access to the single calendar it was created on.
API gotchas
- Targets
https://public-api.luma.com, the domain in Luma's current API reference. The legacylumaprovider targetshttps://api.lu.ma, which Luma keeps available for backward compatibility. public-api.luma.comserves both the current/v1/...routes and the legacy/public/v1/...paths, so requests written for the legacy provider work here unchanged.- The Luma API requires a Luma Plus subscription.
- Luma authenticates with an
x-luma-api-key: API_KEYrequest header. - Luma rate-limits per minute: 200 requests for calendar API keys and OAuth tokens, 500 for organization API keys. Exceeding the limit returns
429 Too Many Requestsand blocks for one minute; honor theRetry-Afterheader. For more details, check Luma rate limits.