Breaking change
An API update that removes or alters functionality in a way that breaks existing integrations. Example: an endpoint is renamed from `/v1/contacts` to `/v2/people`. PURIST monitors API changelog notifications and updates client workflows before breaking changes go live.
How PURIST uses this
This concept is built into every automation we deploy.
When PURIST builds your automation, Breaking change is not an optional consideration it is part of the production standard. Our workflows are tested against edge cases, monitored 24/7, and built to handle what happens when things don't go as expected.
Every client workflow we deploy in the Architecture category is designed with this principle in mind from day one not added as an afterthought.
Complexity level
Requires some familiarity with automation concepts.
Related terms
Versioning (API)
API providers update their APIs over time and version them (v1, v2, v3) to avoid…
API (Application Programming Interface)
A set of rules that allow two software applications to communicate. Most automat…
Integration
A connection between two tools that allows data to flow between them. Can be nat…
See it in action
Want Breaking change built into your automation?
Book a free audit and we'll show you exactly how this applies to your business.
Book free audit →More in Architecture
Keep exploring