> Calendly developer docs. For page Markdown, append .md to any URL.
> Index: https://developer.calendly.com/llms.txt
> API catalog: https://developer.calendly.com/.well-known/api-catalog
> OpenAPI: https://developer.calendly.com/openapi/calendly-api.yaml
> OAuth authorization server: https://calendly.com/.well-known/oauth-authorization-server
> MCP protected resource: https://mcp.calendly.com/.well-known/oauth-protected-resource
> Scheduling MCP endpoint: https://mcp.calendly.com
> Docs search MCP: https://developer.calendly.com/_mcp/server

# November 13, 2026

## Event Type start time increments and buffer times

You can read the start-time increment and the buffer times on an Event Type. You can set them when you create or update a one-on-one Event Type.

### Updated endpoints

* **GET /event_types** – Returns `start_time_increment`, `before_buffer`, and `after_buffer` on each Event Type.
* **GET /event_types/\{uuid}** – Returns the same fields.
* **POST /event_types** – Accepts optional `start_time_increment` (a whole number from 5 to 720, default 30), `before_buffer`, and `after_buffer` (one of 0, 5, 10, 15, 30, 45, 60, 90, 120, 150, or 180, default 0).
* **PATCH /event_types/\{uuid}** – Accepts the same optional fields. Keeps the current value when you omit a field.

### Notes

* These endpoints use the existing `event_types:read` and `event_types:write` scopes.
* `start_time_increment` is `null` for one-off Event Types.