Developer essentials
Versioning
Track compatible changes and plan migrations before behavior changes reach production.
Compatibility contract
Beladed may add fields and enum values without a new version. Clients must ignore unknown response fields and handle unknown optional values safely.
Breaking changes
Breaking changes receive a migration guide, release-note entry, and supported transition window. Pin an API version when the operation reference exposes one.
Follow releases
Review release notes and validate development traffic before upgrading production integrations.
Mark this page