---
title: "Available Meetings"
method: GET
path: "/v2.0/calendar/meetings/available"
tags: ["Calendar V2 API"]
---

# Available Meetings

`GET /v2.0/calendar/meetings/available`

## Request

- Base URL: `https://api.lofty.com`
- URL: `https://api.lofty.com/v2.0/calendar/meetings/available`
- Auth: none required
- TypeScript: <https://skmtc.dev/lofty/apis/lofty-service-open-apis/docs/v2.0/calendar/meetings/available/get.ts> (a function with typed inputs; its response is checked against the schema)

Returns available meeting time slots within the given time range, sorted by startTime ascending.

Notes:
- Either startTime (ISO 8601) or startTimeMs (millisecond timestamp) must be provided; same for endTime / endTimeMs. When both forms are provided for a field, the string form takes precedence.
- The resolved start time must be later than the current server time.
- The resolved end time must be later than the resolved start time.
- The range between start and end must not exceed 90 days.
- At most 'limit' slots are returned; the envelope also includes the total count.

## Query parameters

- `startTime` string
- `endTime` string
- `startTimeMs` integer
- `endTimeMs` integer
- `timeZoneCode` string
- `limit` integer

## Headers

- `Authorization` string, required

## Response `200`

Available meeting slots with total count.

- AvailableMeetingsResponseEnvelope: Response envelope for GET /v2.0/calendar/meetings/available. Wraps the available meeting slots under the 'data' field.
  - `data` AvailableMeetingsResponseV2: Available meeting time slots response
    - `total` integer: Total number of available meeting slots
    - `slots` AvailableMeetingSlotV2[]: List of available meeting slots (sorted by startTime ascending, up to limit)
      - `startTime` string: Slot start time (ISO8601, e.g. 2024-01-15T09:00:00-08:00)
      - `endTime` string: Slot end time (ISO8601, e.g. 2024-01-15T10:00:00-08:00)
      - `startTimeMs` integer: Slot start time as Unix timestamp in milliseconds
      - `endTimeMs` integer: Slot end time as Unix timestamp in milliseconds

## Other responses

- `400`: Invalid time range or parameters (20012 INVALID_PARAMETER).
- `401`: Missing or invalid authentication token.
- `500`: Internal server error.

---

[API](https://skmtc.dev/lofty/apis/lofty-service-open-apis.md) - [All operations](https://skmtc.dev/lofty/apis/lofty-service-open-apis/llms.txt) - [OpenAPI document](https://skmtc.dev/lofty/apis/lofty-service-open-apis/revisions/23e640467118?raw)