Meetings

Relay availability for an invited guest (organizer path)

Allows the meeting organizer to submit availability slots on behalf of an invited guest who is communicating out-of-band (e.g. via a conversational agent). The slots are recorded against the guest's existing invite/participant record — relaying does not implicitly invite an email that has not already been added to the meeting. Replaces the guest's prior relayed-or-submitted slots (last-write-wins). If the guest has a connected calendar, their real-time free/busy still takes precedence over relayed data per the standard overlap logic.

post/api/meetings/{id}/relay-availability

Request

  • Base URL: https://api.wondercal.com
  • URL: https://api.wondercal.com/api/meetings/{id}/relay-availability
  • Auth: HTTP bearer

Path parameters

idstring required

Meeting ID

Request body

guestEmailstring email required

The invited guest's email address. Must match an existing (non-revoked) invite on this meeting.

Example request

{
  "slots": [
    {
      "start": "2026-02-25T09:00:00.000Z",
      "end": "2026-02-25T10:00:00.000Z"
    }
  ]
}

Response

Availability relayed

Example response

{
  "data": {
    "saved": true
  }
}

Changes

No recorded changes to this operation across all 1 revision of this API.