List, retrieve (including public lookup by username and slug), and update Cal.com event types via the API v2 /v2/event-types endpoints.

Documented steps

1. Set header cal-api-version: 2024-06-14 on all /v2/event-types requests (list, get-by-id, update); a missing or wrong value selects an older API version.
2. To list event types, send GET https://api.cal.com/v2/event-types with optional query params username, usernames (comma-separated), orgSlug or orgId, and sortCreatedAt=asc|desc.
3. For a public lookup by username and slug, send GET https://api.cal.com/v2/event-types?username=<username>&eventSlug=<slug> — Authorization is optional for publicly bookable event types.
4. Include Authorization: 'Bearer <TOKEN>' on list/get when you need hidden event types; hidden ones are excluded unless the caller is authenticated as the owner.
5. Parse the list response {status:'success', data:[...]} — objects with id, title, slug, lengthInMinutes, bookingFields, locations, etc.
6. To fetch a single event type by numeric ID, send GET https://api.cal.com/v2/event-types/{eventTypeId} with Authorization and cal-api-version: 2024-06-14; this path always requires authorization (owner, host, team admin, org admin).
7. To update, send PATCH https://api.cal.com/v2/event-types/{eventTypeId} with Authorization (OAuth needs EVENT_TYPE_WRITE) and cal-api-version: 2024-06-14, sending only fields to change (title, slug, lengthInMinutes, bookingFields, locations, hidden, scheduleId).
8. Do not attempt to change teamId or parentId — they are immutable in v2 and such updates are rejected.
9. When replacing bookingFields, send the complete set — the array replaces rather than merges with the existing configuration.
10. Check the PATCH response {status, data:{...updated event type...}} before relying on the change elsewhere (e.g. before querying /v2/slots with new duration options).
11. Docs: https://cal.com/docs/api-reference/v2/event-types/get-all-event-types