Update an event type
Headers
Must be set to 2024-06-14
value must be Bearer <token>
where <token>
either managed user access token or api key prefixed with cal_
Path Parameters
Body
If you want that user can choose between different lengths of the event you can specify them here. Must include the provided lengthInMinutes
.
Locations where the event will take place. If not provided, cal video link will be used as the location.
Custom fields that can be added to the booking form when the event is booked by someone. By default booking form has name and email field.
If true, person booking this event't cant add guests via their emails.
Number representing length of each slot when event is booked. By default it equal length of the event type. If event length is 60 minutes then we would have slots 9AM, 10AM, 11AM etc. but if it was changed to 30 minutes then we would have slots 9AM, 9:30AM, 10AM, 10:30AM etc. as the available times to book the 60 minute event.
Minimum number of minutes before the event that a booking can be made.
Time spaces that can be pre-pended before an event to give more time before it.
Time spaces that can be appended after an event to give more time after it.
If you want that this event has different schedule than user's default one you can specify it here.
Limit how many times this event can be booked
This will limit your availability for this event type to one slot per day, scheduled at the earliest available time.
Limit total amount of time that this event can be booked
Limit how far in the future this event can be booked
Offset timeslots shown to bookers by a specified number of minutes
Should booker have week, month or column view. Specify default layout and enabled layouts user can pick.
Specify how the booking needs to be manually confirmed before it is pushed to the integrations and a confirmation mail is sent.
Create a recurring event type.
Create an event type with multiple seats.
Customizable event name with valid variables: {Event type title}, {Organiser}, {Scheduler}, {Location}, {Organiser first name}, {Scheduler first name}, {Scheduler last name}, {Event duration}, {LOCATION}, {HOST/ATTENDEE}, {HOST}, {ATTENDEE}, {USER}
Response
success
, error
Was this page helpful?