---
title: "Relay availability using a guest's invite token (guest-agent path)"
method: POST
path: "/api/meetings/relay-availability"
tags: ["Meetings"]
---

# Relay availability using a guest's invite token (guest-agent path)

`POST /api/meetings/relay-availability`

## Request

- Base URL: `https://api.wondercal.com`
- URL: `https://api.wondercal.com/api/meetings/relay-availability`
- Auth: none required

Allows a caller presenting a guest's invite token to submit availability on that guest's behalf — e.g. the guest's own conversational agent responding to an invite programmatically. This endpoint does not require a WonderCal Bearer token; the invite token itself is the credential and is scoped to exactly one invite. Rejected if the invite has been revoked, or if it has been claimed by a different WonderCal account (the OAuth account takes precedence once claimed).

## Request body

- object
  - `meetingId` string, required: Meeting ID.
  - `inviteToken` string, required: The guest's invite token, from their invite email link.
  - `slots` AvailabilitySlot[], required: Array of availability time slots to record for the guest.
    - `start` string, date-time, required: Slot start time in ISO 8601 format
    - `end` string, date-time, required: Slot end time in ISO 8601 format
    - `isBlocked` boolean: Whether this slot is blocked (calendar event)

## Response `200`

Availability relayed

- object
  - `data` object
    - `saved` boolean

## Other responses

- `400`: Validation error
- `403`: Invite is revoked or claimed by another account
- `404`: Meeting not found, or invite token not recognized for this meeting
- `429`: Rate limit exceeded. The Retry-After header indicates how many seconds to wait before retrying.

---

[API](https://skmtc.dev/wondercal/apis/wondercal-api.md) · [All operations](https://skmtc.dev/wondercal/apis/wondercal-api/llms.txt) · [OpenAPI document](https://skmtc.dev/wondercal/apis/wondercal-api/revisions/4889176a380f?raw)