The API is versioned in the path (/v1). Backwards-compatible changes — new endpoints, new optional fields, new enum values — ship without a version bump, so write clients that ignore unknown fields.
Breaking changes ship under a new version prefix (/v2) and the previous version stays supported during a published deprecation window. Subscribe to the changelog to track additions.