Update a team event type
Update a team event type
Authorizations
Use the Authorization header with Bearer scheme.
Examples:
- API Key: Authorization: Bearer calid_xxxxx
Path Parameters
Numeric team identifier.
x > 142
Numeric team event type identifier.
x > 17
Body
Human-readable title for the event type shown in booking pages and calendars.
4 - 255"30 Minute Discovery Call"
Unique URL slug for the event type under the owner account.
4 - 100"discovery-call-30"
Optional event type description shown to bookers.
"A short introductory call to discuss your goals and next steps."
Interface language used for the booking experience.
"en"
Sort position used when listing multiple event types.
0
Location or conferencing configuration payload for this event type. Each item type must be one of the supported location type enum values.
Meeting duration in minutes.
x >= 1030
Offset in minutes added to generated slot start times.
0
Whether the event type should be hidden from public listings.
false
IANA timezone used when event type timezone is locked.
"Asia/Kolkata"
Availability period strategy for booking this event type.
UNLIMITED, ROLLING, ROLLING_WINDOW, RANGE "UNLIMITED"
Start date-time boundary for limited booking windows.
"2026-05-01T00:00:00.000Z"
End date-time boundary for limited booking windows.
"2026-05-31T23:59:59.000Z"
Number of days allowed for period-based booking limits.
30
Whether period day counting should use calendar-day boundaries.
true
Whether new bookings require organizer confirmation.
false
Whether pending confirmation should block the slot from other bookings.
false
Whether confirmation is enforced for bookers using free email domains.
false
Whether the booker must verify email before finalizing booking.
false
Recurring event configuration payload.
Whether attendees are prevented from adding guests.
false
Whether internal calendar notes are hidden from attendees.
false
Whether detailed calendar event metadata is hidden from attendees.
false
Minimum notice in minutes required before a slot can be booked.
x >= 0120
Buffer time in minutes blocked before each booking.
0
Buffer time in minutes blocked after each booking.
0
Maximum seats available per slot for seat-based events.
5
Whether only the first available slot should be displayed to bookers.
false
Whether guests are prevented from cancelling bookings.
false
Whether guests are prevented from rescheduling bookings.
false
Whether hosts are prevented from cancelling bookings for team events.
false
Whether hosts are prevented from rescheduling bookings for team events.
false
Whether seat-based events should show attendee details to other attendees.
false
Whether remaining seat availability count should be shown to bookers.
true
Scheduling strategy for owner/team assignment.
ROUND_ROBIN, COLLECTIVE, MANAGED "COLLECTIVE"
Schedule identifier linked to this event type.
1
Price amount in the smallest currency unit for paid events.
0
ISO currency code used when price is set.
"usd"
Custom interval in minutes between suggested slots.
15
Arbitrary metadata payload stored with the event type.
URL to redirect bookers to after successful booking.
"https://example.com/booking-success"
Whether booking query parameters should be appended to the success redirect URL.
true
Booking limits configuration payload.
Allowed duration limits configuration payload.
Whether this event type can be booked instantly for near-immediate meetings.
false
Number of seconds before an instant meeting offer expires.
90
Whether all team members should be assigned for this event type.
false
Whether round-robin members should be selected using a segment query.
false
Segment query payload used for round-robin member assignment.
Whether destination calendar email should be derived from event type settings.
false
Whether weighted round-robin distribution is enabled.
false
Maximum lead threshold used for assignment logic.
100
Whether no-show bookings should be included in round-robin calculations.
false
Whether past bookings are eligible for rescheduling.
false
Whether organizer email is hidden from attendees.
false
Maximum number of active bookings allowed per booker.
3
Whether over-limit bookers should be offered reschedule instead of blocking.
false
Custom reply-to email used in booking communications.
"replyto@example.com"
Custom color settings for the event type.
Whether reschedules should keep the same round-robin host.
false
Whether booking flow should prioritize the booker timezone.
false
Schedule identifier used to restrict availability for this event type.
2
Full replacement list of user-managed booking fields.
Related topics
Update an event typeDelete a team event typeGet a team event typeList team event typesCreate a team event type