Endpoint
Request Headers
| Header | Required | Description |
|---|---|---|
Authorization | Yes | Bearer <your-api-key> |
This endpoint does not require the
x-meetergo-api-user-id header as it queries availability for a meeting type.Query Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
meetingTypeId | string | Yes | The ID of the meeting type to check availability for |
start | string | Yes | Start date in YYYY-MM-DD format |
end | string | Yes | End date in YYYY-MM-DD format |
hostIds | string[] | No | Comma-separated list of host IDs to filter availability |
queueId | string | No | Queue ID for round-robin meeting types |
meetingDuration | number | No | Duration in minutes (for meeting types with multiple options) |
timezone | string | No | Timezone for returned slots (e.g., Europe/Berlin) |
existingAppointmentId | string | No | Appointment ID when rescheduling (ignores its blocked time) |
resourceChannelIds | string[] | No | Filter by specific resource channels (e.g., meeting rooms) |
troubleshoot | boolean | No | When true, returns diagnostic information |
Examples
Response
Success (200 OK)
| Field | Description |
|---|---|
slots | Array of available time slots grouped by date |
slots[].date | The date in ISO 8601 format |
slots[].times | Array of available start times in ISO 8601 format |
timezone | The timezone used for the response |
Error Responses
400 Bad Request - Meeting Type Not Found
401 Unauthorized
Notes
- The response respects the meeting type’s buffer times, minimum booking notice, and maximum advance booking settings
- For round-robin meeting types, the availability represents the combined availability of all hosts in the queue
- When
hostIdsis provided, only those specific hosts’ availability is considered
Related Endpoints
Availability Concepts
Learn about availability schedules and configuration
Create Booking
Book a time slot