Changelog and Versioning

Versioning

The API uses URI versioning. Every endpoint lives under a version prefix,
currently /v1.

• Additive changes do not change the version. New optional fields and new
  endpoints can appear under /v1, so build your integration to ignore
  fields it does not recognize.
• Breaking changes ship under a new major version, such as /v2. The
  previous version stays supported through a published deprecation window.

Deprecation policy

When a version is scheduled for retirement, Button will:

• Announce it in this changelog with a retirement date.
• Support the retiring version for a minimum of 6 months from the
  announcement.
• Keep the previous major version available throughout that window so you
  have time to migrate.

Changelog

Entries are dated, newest first.