Headers
Must be set to 2024-08-13
value must be Bearer <token>
where <token>
is api key prefixed with cal_ or managed user access token
For platform customers - OAuth client secret key
For platform customers - OAuth client ID
Body
Accepts different types of booking input: Create Booking (Option 1), Create Instant Booking (Option 2), or Create Recurring Booking (Option 3)
The start time of the booking in ISO 8601 format in UTC timezone.
"2024-08-13T09:00:00Z"
The attendee's details.
Booking field responses consisting of an object with booking field slug as keys and user response as values for custom booking fields added by you.
{ "customField": "customValue" }
The ID of the event type that is booked. Required unless eventTypeSlug and username are provided as an alternative to identifying the event type.
123
The slug of the event type. Required along with username / teamSlug and optionally organizationSlug if eventTypeId is not provided.
"my-event-type"
The username of the event owner. Required along with eventTypeSlug and optionally organizationSlug if eventTypeId is not provided.
"john-doe"
Team slug for team that owns event type for which slots are fetched. Required along with eventTypeSlug and optionally organizationSlug if the team is part of organization
"john-doe"
The organization slug. Optional, only used when booking with eventTypeSlug + username or eventTypeSlug + teamSlug.
"acme-corp"
An optional list of guest emails attending the event.
Deprecated - use 'location' instead. Meeting URL just for this booking. Displayed in email and calendar event. If not provided then cal video link will be generated.
"https://example.com/meeting"
One of the event type locations. If instead of passing one of the location objects as required by schema you are still passing a string please use an object.
You can store any additional data you want here. Metadata must have at most 50 keys, each key up to 40 characters, and string values up to 500 characters.
{ "key": "value" }
If it is an event type that has multiple possible lengths that attendee can pick from, you can pass the desired booking length here. If not provided then event type default length will be used for the booking.
30
Routing information from routing forms that determined the booking assignment. Both responseId and teamMemberIds are required if provided.
{
"responseId": 123,
"teamMemberIds": [101, 102]
}
Email verification code required when event type has email verification enabled.
"123456"