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 host user IDs. For round-robin meeting types, pass all host IDs from the queue |
queueId | string | No | Queue ID for round-robin meeting types |
calculationMethod | string | No | anyone (default) or everyone. With anyone, a slot is available if any host is free. With everyone, all hosts must be free simultaneously |
meetingDuration | number | No | Duration in minutes (for meeting types with multiple duration options) |
timezone | string | No | Timezone for returned slots (e.g., Europe/Berlin) |
channel | string | No | Meeting channel (e.g., local, zoom, phone). Uses channel-specific availability if configured |
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 about blocked slots |
Examples
Response
Success (200 OK)
| Field | Description |
|---|---|
timezone | The timezone used for the response |
timeframes | Array of available time windows (UTC) |
timeframes[].start | Start of the available window in ISO 8601 (UTC) |
timeframes[].end | End of the available window in ISO 8601 (UTC) |
dates | Array of available dates with bookable spots |
dates[].date | The date in YYYY-MM-DD format |
dates[].spots | Array of bookable time slots for the date |
dates[].spots[].startTime | Start time in ISO 8601 with timezone offset |
earliestAvailableDate | The earliest date with available spots (YYYY-MM-DD) |
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, pass
hostIdswith all team members andqueueIdto get the combined availability of the team - When
hostIdsis provided, only those specific hosts’ availability is considered - Connected calendar events (Google Calendar, Outlook, etc.) automatically block the corresponding time slots
Related Endpoints
Availability Concepts
Learn about availability schedules and configuration
Create Booking
Book a time slot