Create a new appointment in a connected calendar after explicit user confirmation; checks the slot is still free right before writing

Creates an appointment in a connected calendar after explicit user confirmation (confirm: true). Provide exactly one of end or durationMinutes. idempotencyKey is optional - the same value sent again returns the already-created event instead of a second write. The slot is checked to still be free right before writing; the response is the freshly read event, the same shape as GET .../events/{eventId}.

post/v1/integrations/{id}/events

Request

  • Base URL: https://volai.cz
  • URL: https://volai.cz/v1/integrations/{id}/events
  • Auth: HTTP bearer

Path parameters

idstring required

Request body

calendarIdstring required

Calendar id from list_calendars, for example primary.

busyCalendarIdsstring[]

Other calendars in the same connection whose events also block a slot; nothing is written into them, so read-only calendars are fine. At most 4, without duplicates and without calendarId itself.

startstring date-time required

Start of the appointment, RFC 3339 with an offset.

endstring date-time

End of the appointment, RFC 3339 with an offset. Provide exactly one of end or durationMinutes.

titlestring required

Event title shown in the calendar.

descriptionstring

Additional details about the appointment, shown next to the title in the calendar entry.

idempotencyKeystring

Optional booking key without control characters, semicolons, commas or backslashes. Sending the same value again returns the already-created event instead of creating a second one.

confirmboolean

Must be true, confirming the user has explicitly approved this exact date, time and title. Without it the request is rejected with calendar_confirmation_required.

Response

The newly created event, freshly read back from the provider

Changes

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