## Versioning

Breaking changes can be disruptive and we take versioning very seriously. If we require sunsetting a legacy endpoint, we'll notify you with sufficient lead time to migrate. We recommend implementing against the latest endpoints documented in the Brex API.

### Breaking changes

We don't consider the following types of changes as breaking changes:

* New endpoints
* New read-only or optional fields
* Endpoints or fields marked as deprecated
* New enum constants


**Note:** Your code should be able to handle new types of responses. For example, please ensure that you design your code to handle unknown enum types and new fields in responses.