Skip to main content
Welcome to the tipee API changelog. This tab tracks how the API evolves, for the version currently selected in the version dropdown:
  • Changelog for version — the detailed history of changes, grouped by date.
What each version brought endpoint by endpoint is not listed here: it is carried by a badge next to the endpoint in the API Reference tab, described in the Versioning guide.

API versions

How to read the changelog

The changelog contains all changes applied to the endpoints : the ones from the release of the current version and the possible changes in the future as well. Each dated entry lists the affected endpoints and describes every change with a badge:
added
Next to an endpoint title: the endpoint is new in this version.
changed
Next to an endpoint title, in the preview version: the endpoint is already part of a stable version, and the preview brings upcoming changes to its contract; the rows below say which.
removed
Next to an endpoint title: the endpoint itself is gone in this version, and every one of its changes is only there to describe how to move away from it.
requestresponse
Which part of the contract the change applies to.
operation
The change applies to the endpoint itself rather than to one side of its contract: the endpoint is renamed, its method changes, or it is deprecated.
breaking
The change is not backward compatible: your integration may require an update. Breaking changes normally only appear between stable versions; exceptionally, a stable endpoint may receive one when a major bug has to be fixed, in accordance with the API Terms of Use.
The preview version never flags breaking changes: preview endpoints carry no stability guarantee and may change without prior notice — see the Versioning guide.

Stay informed

Subscribe to Changelog notifications to be notified when a new stable version of the tipee API is released, when an endpoint will begin to be deprecated, and of bug or security fixes that introduce a breaking change.