# Backward compatibility

Breaking changes can impact existing integrations and require adjustments. These are marked with a **breaking changes** badge in the changelog and include:

Category
Change
Operation removal
Removing an API operation.
Request
Remove or rename a field, make optional fields required, remove 
oneOf
.
Response
Remove or rename a field, change HTTP status code, remove 
oneOf
.
Type changes
Change request or response data types.
HTTP headers
Add required headers or remove existing ones.
Enum updates
Remove enum values.
Errors
Change existing error codes.
Validation rules
Add stricter or new rules.
Authentication and authorization
Change requirements.
Non-breaking changes do not affect existing integrations and preserve backward compatibility:

Category
Change
Request
Add new optional fields, change required fields to optional.
Response
Add new optional fields, change optional fields to required.
HTTP headers
Add new optional headers, change header case.
Field length
Expand maximum length.
Identifier format
Change prefixes or formatting.
Webhook events
Add new opt-in event types.
Webhook schema
Add new fields.
Rate limiting
Changes communicated at least one month in advance.
New enum values can appear in any field whose description says `The list of enum values may be extended without notice.` These values can be added without a new API version. Handle unknown values in a default branch instead of treating them as errors. In responses and webhooks, enums without this note get new values only in a new API version. A field without this note can become extensible only by gaining this note. An extensible field may later be documented as a fixed set.

Deprecated operations

When an operation is replaced, the old one keeps working for a support period and is marked **Deprecated** in this reference. Its description names the replacement and the last day it is supported. Responses from a deprecated operation include the `Sunset` header with the end of that day (UTC), for example `Sunset: Sun, 28 Feb 2027 23:59:59 GMT`. Move to the replacement before that date: after it, the operation can be removed.

For help, contact us.