Help

API keys

Your team can call the QuantiMeet API with its own key, on its own address.

BetaPer-team API keys, beta: each team's keys work on its own address only.

Make a key

1. Signed in, open your-team.quantimeet.com/settings/developer/api-keys and create a key.
2. Copy it when it is shown. QuantiMeet keeps only a scrambled form of it, so it cannot show it again.
3. A key starts with cal_. Treat it like a password.

Call the API

Every request goes to your team's own address, https://your-team.quantimeet.com/api/v2, with the key in an Authorization header. This lists your event types:

curl -H "Authorization: Bearer YOUR_API_KEY" -H "cal-api-version: 2024-06-14" https://your-team.quantimeet.com/api/v2/event-types

Replace your-team with your team's address and YOUR_API_KEY with your key. On Windows, type curl.exe. To test a key, /api/v2/me answers with your own profile. The same key on quantimeet.com or on another team's address is refused (401).

What your address answers

These parts of the API: me, event types, bookings, slots, schedules, calendars, conferencing, destination and selected calendars, and time zones. Anything else answers 404, "This endpoint is not available on a team host." You connect a calendar in your dashboard, not through the API.

Send the version each part expects in a cal-api-version header: 2024-06-14 for event types, 2024-08-13 for bookings, 2024-09-04 for slots and 2024-06-11 for schedules.

LiveWebhooks are live: add one on an event type's Webhooks tab, and it receives a signed message for each booking and each cancellation of that event type.

Limits

Each team's limits are its own, and responses carry rate-limit headers. There are no per-request fees and no overage charges. Moving a round-robin booking to another host is not available: the API answers 501.