Docs
← chronapilot.com v 2026-05-12
API reference · Invitations
inv_

Invitations

ICS-based attendee invitations with delivery + response tracking.

Endpoints

POST /v1/invitations Send invitations
GET /v1/invitations/{id} Retrieve an invitation
POST /v1/invitations/{id}/respond Attendee response

Object shape

The invitation tracks an attendee's lifecycle for one event — email delivery, response status, ICS sequence number.

FieldTypeDescription
idstringPrefixed inv_.
event_idstringAssociated event.
organizer_user_idstringEvent organizer.
attendee_emailstringAttendee email.
attendee_namestring?Display name.
attendee_user_idstring?Set if the attendee is also a ChronaPilot user.
response_tokenstringUnique token for response URLs.
statusstringemail_queued, email_sent, email_delivered, opened, responded, bounced.
email_typestringinvite, update, cancel.
ical_sequenceintegerRFC 5545 SEQUENCE.
responded_atdatetime?When the attendee responded.
unsubscribedbooleanTrue if the attendee opted out.

Send invitations

HTTP
POST /v1/invitations
JSON
{
  "event_id": "evt_1abc2def3ghi",
  "attendees": [
    {"email": "sarah@example.com", "name": "Sarah Chen"},
    {"email": "doctor@smiledental.com", "name": "Dr. Smith"}
  ]
}

Each attendee gets an ICS-attached email (delivered via Azure Communication Services) plus an in-app push if they're also a ChronaPilot user.

Retrieve

HTTP
GET /v1/invitations/{id}

Attendee response

HTTP
POST /v1/invitations/{id}/respond
JSON
{ "status": "accepted" }

statusaccepted | declined | tentative. The endpoint can also be hit by the attendee with the response_token query parameter — used by the email's accept/decline links.

Reference implementation