Contracts
Determine which fields, events and error codes are part of a stable integration version.
Treat response fields, event names and behavior as integration contracts. Breaking changes should be visible, plannable and testable.
Determine which fields, events and error codes are part of a stable integration version.
Plan migration and communication before an old variant is no longer supported.
Prevent unexpected breaking changes within the same version and make extensions backward compatible where possible.
Turn contract and chain tests at SDK-, API and dependency upgrades.
Testing →