additive change
Evolving an API only by adding things, such as a new optional field or operation, while everything existing keeps its meaning.
In more detail
It is the cheapest way to change a contract, but not automatically safe: strict parsers can reject unknown fields. Document defaults and whether an omitted field differs from a null value.
Related terms
- backward compatibility — The property that a new version of an interface still works for clients written against the old one.
- nullability — Whether a field may hold null, an explicit no value, and how that differs from the field being absent.
- breaking change — A change that makes existing users of a program or interface stop working until they change something too.
Taught in
- Versioning APIs — Modern API Architecture: REST, GraphQL & gRPC
- Contract Testing — Modern API Architecture: REST, GraphQL & gRPC