Versioning and deprecations

Use the curated API reference and this versioning guide as the customer-facing contract and change history. Pin or review the API contract used by an integration; do not infer version support from an old prose example.

A route or field is not deprecated merely because it is absent from this curated guide. Conversely, this guide does not promise compatibility for internal or excluded route classes. Check the versioning guide and current reference before upgrading, and contact Support when a documented contract changes unexpectedly.