Releases

Versioning

We support several endpoint versions at any given time. For new integrations, we recommend using the version indicated in the URL of the endpoint (e.g. /v2.0/).

How endpoint versioning occurs

• We roll out backward-compatible changes into the existing endpoint version.
• We roll out backward-incompatible changes into a new endpoint version.
• We will notify you of endpoint changes in the API Change Log.

Changes

• You should expect that we will add elements to released endpoint versions.
• You should never expect us to remove, rename, or change the data type of an element in any released endpoint version.
• You should expect that the order of our response data may change at any given time for every released endpoint version.

Retiring a version

• You should expect that older released endpoint versions will be retired as new versions come online.
• You should expect that we will always give ample notice before a released endpoint version is to be retired.

Please report any issues to apisupport@bcdtriptech.com.