Changelog
Back to All
Added

API versioning

October 14th, 2026

Name the API version your integration was built against in the new Ekko-Version header. The API responds the way that version behaves, so a change we make later reaches you only when you move to a new version.

What's new

  • Sending a version: pass Ekko-Version: 2026-10-06.pangolin on every request, from every part of your integration. Every response carries an Ekko-Version header with the version it was served at.
  • Required header: the header is required. Until the grace period ends, a request without it is served at the latest version. After that, it's refused with a 400 and API_VERSION_REQUIRED.
  • Invalid versions: a value that is not a released version returns a 400 with API_VERSION_INVALID. details.latest_version names the current version.
  • Version names: a release date and an animal. The animal changes only when a release contains a breaking change.

See Versioning for which changes ship without a new version and how to move to a new one.