How Do You Query Event Types and Availability Through the API?

Listing Event Types #

GET /api/v1/event-types?active=true&limit=50

Returns the event types visible to the authenticated key, each with its identifier, name, slug, duration, location type, public URL, and the identifier of the availability schedule it uses. Results are paginated with a cursor returned as next_cursor.

Fetching One Event Type #

GET /api/v1/event-types/{id}

The single-resource response additionally includes booking questions with their slugs and types, buffer settings, and any limits in force. This is the endpoint to call when building your own booking interface, since it tells you exactly which fields to render.

Requesting Available Slots #

GET /api/v1/event-types/{id}/slots
  ?start=2026-09-07&end=2026-09-14&timezone=Asia/Kolkata

Returns bookable start times with every rule already applied: working hours, overrides, calendar conflicts, buffers, notice, window, and limits. The maximum span per request is thirty-one days.

Response Shape #

{
  "timezone": "Asia/Kolkata",
  "slots": [
    { "start": "2026-09-07T09:00:00+05:30", "end": "2026-09-07T09:30:00+05:30" },
    { "start": "2026-09-07T09:30:00+05:30", "end": "2026-09-07T10:00:00+05:30" }
  ],
  "next_cursor": null
}

Freshness #

Slot responses reflect the moment of the call. Do not cache them for more than a minute, and always expect a booking attempt on a stale slot to fail with a conflict error, which is the guarantee that prevents double booking.

Availability Schedules #

Named schedules are exposed at /api/v1/availability-schedules for reading and updating working hours and date overrides programmatically.