---
sidebar_label: 'Breaking changes'
sidebar_position: 5
---

# Breaking changes

Future Ordering is committed to maintaining backward compatibility and will announce any breaking change well in advance of a required upgrade. Announcements are made through request and response headers following the [deprecation header draft RFC](https://datatracker.ietf.org/doc/html/draft-dalal-deprecation-header-03) and may also be communicated through additional channels such as your Customer Success Manager or Account Manager.

The following changes are considered breaking:

- Renaming or removing a request or response parameter
- Changing the type of a request or response parameter
- Renaming or removing a request or response header
- Making request validation more strict
- Removing options from an enum
- Modifying HTTP response codes

## Non-breaking changes

The following changes are not considered breaking and do not follow the breaking change procedure:

- Adding optional new parameters to requests
- Adding new parameters to responses
- Adding new request headers
- Reordering parameters in responses
- Softening validation rules for request parameters
- Increasing the set of possible enumeration values