# Versioning and deprecation > API v1 only grows: fields and endpoints are added, never renamed or removed. Breaking changes get a new version and at least 6 months' notice. ## What can change in v1 - New endpoints, new optional request fields, new response fields, new webhook events and new error codes on new routes. Write your client to ignore fields it doesn't know. - Never: a removed or renamed field, a changed type or meaning, a new required request field, or a changed error code on an existing route. ## Webhook payload versions Each endpoint chooses its payload version (`api_version`). `2026-09-01` is frozen; `2026-11-01` adds ids, the invite, band counts, `livemode` and the `role.*` events. Older versions keep being delivered as they are. ## Deprecation A breaking change ships as a new version. The old version keeps working for at least 6 months after the notice, which goes to workspace owners by email and to the [Changelog](/developers/changelog).