A breaking change is a software change that makes existing applications, integrations, or dependent code stop working as expected. It removes backward compatibility, so users may need to update their code before adopting the new version. The impact depends on what a system publicly promises, including APIs, libraries, command-line tools, data formats, and documented behavior.
Breaking Change
What Is a Breaking Change?
A breaking change is a software update that causes existing code, integrations, or apps to stop working as expected. It removes backward compatibility, meaning a previously valid request, dependency, or workflow now needs changes.
Breaking Changes vs Non-Breaking Changes
The key question is whether existing consumers can keep working without modification.
| Change | Typical result |
|---|---|
| Remove an endpoint, rename a field, or add a required parameter | Breaking change |
| Change a data type, default value, authentication rule, or response behavior | Usually breaking |
| Add an optional field or new endpoint | Usually non-breaking |
How to Identify a Breaking API Change
An API change affects how one application communicates with another through its published interface.
- List the public endpoints, fields, commands, and documented behaviors.
- Check which parts client applications depend on.
- Test requests from older client versions.
- Review changed defaults, permissions, and error responses.
- Document required migration steps and classify the release.
How to Release Breaking Changes Safely
A major version signals risk, but it does not replace practical migration guidance.
- Announce deprecations before removal.
- Offer parallel API versions when practical.
- Publish examples, release notes, and a migration guide.
- Use contract tests and prepare a rollback plan.
Building Compatible Updates with Emergent
Emergent can help teams describe an update, implement it, and test affected user flows before release. Learn more about app design and development, compare AI agent builders, or browse the software glossary. Build and test compatible app updates with Emergent.
Frequently Asked Questions
Your Questions, Answered
This will automatically populate, don't change
Don't change this element unless you know what you are doing
What is a breaking change?
A breaking change is a software change that makes a previously working integration, application, or dependency fail or require updates.
What is an API change?
An API change modifies the rules an application uses to communicate with another service, such as its endpoints, parameters, responses, or authentication.
What does API stand for?
API stands for Application Programming Interface. It is a defined way for software systems to exchange requests and data.
Can you give me an example of an API?
A weather API can let an app request a forecast for a location and receive structured weather data in response.
Start Building
on Emergent today
on Emergent today
Start Building
