API Version control

If and when we release an updated version of an API that would result in a breaking change, we will associate a version number to that API and include reference to that our in our documentation.

Where a new version is introduced, the API name itself will remain the same but the URI calling that API will need to include the appropriate version number for that resource as a parameter

For example, the call for version 2 of the AbsenceHeader API would look like this:

/api/AbsenceHeaders?version=v2

Deprecation

Should Zellis have a need to deprecate a specific version of an API we will update the release notes for a given release with a stated target date for deprecation.  The intention would be to provide at least six months (one full HCM release cycle) notice of a pending deprecation.