Respond to an invitation
Accepts, declines or tentatively accepts an invitation.
Permission
The key must be granted calendar.events.write
A key without it gets 403 insufficient_scope, with the missing permission named in details.
Read access to the calendar is enough; you do not need write to answer an invitation. Your address must be on the attendee list, or this returns 404.
Path parameters
| Field | Type | Description |
|---|---|---|
calendar_id required |
string | |
id required |
string |
Request body
| Field | Type | Description |
|---|---|---|
response required |
string |
Your answer to the invitation.
accepteddeclinedtentative
|
comment |
string | A note for the organiser, sent with the reply and not stored. |
Request
curl https://api.veruapis.com/v1/calendars/:calendar_id/events/:id/rsvp \
-X POST \
-H "Authorization: Bearer vak_live_..." \
-H "Idempotency-Key: $(uuidgen)"
Idempotency-Key is required on every write. Retrying with the same key returns the original response rather than repeating the operation, so a timeout is something you retry rather than something you investigate.
Response
{
"data": { ... },
"meta": { "request_id": "req_01j8z9...", "timestamp": "2026-09-02T10:00:00Z" }
}
A worked example for this endpoint has not been written yet.
Every failure uses the same shape, with a stable string code you can branch on. See the error reference.
Related
- POST Create a calendar
- POST Create an event
- DELETE Delete a calendar
- DELETE Delete an event
- POST Find a time that works
- POST Query free/busy
- GET Get a calendar
- GET Get an event
- GET List events in a calendar
- GET List calendars
- GET List events
- PATCH Update a calendar
- PATCH Update an event