API reference/GET /public/schedules/{public_scheduling_boundary_id}/meeting-types

GET /public/schedules/{public_scheduling_boundary_id}/meeting-types

publicoptional rc

List public meeting types visible through a public scheduling boundary.

This endpoint may be called anonymously. Send an optional requester credential as Authorization: Bearer rc_... to reveal meeting types allowed for that verified requester context.
Suggested times are not holds. Recheck happens when the requester submits the proposal.

Request

GET /public/schedules/{public_scheduling_boundary_id}/meeting-types HTTP/1.1

Response

Returns 200 OK with the response body below.

200 OK · example

HTTP/1.1 200 OK
Content-Type: application/json

{
  "meeting_types": [
    {
      "public_meeting_type": "intro-call",
      "name": "Intro call",
      "description": "Meet the team.",
      "duration_minutes": 30,
      "suggested_times": [
        {
          "start": "2026-07-08T14:00:00.000Z",
          "end":   "2026-07-08T14:30:00.000Z",
          "rank":  1,
          "source": "allocation"
        }
      ]
    }
  ]
}

Errors

Code	Description
`404`	Calendar owner or booking id not found.
`429`	Rate limit exceeded. Per-key limits: POST /v1/availability/search → 300 req/min; POST /v1/holds, POST /v1/bookings, and /v1/bookings/{hold_id}/confirm → 120 req/min each. A global fallback of 600 req/min per IP applies to all other endpoints. Read the Retry-After header for the exact backoff in seconds.