Versioning
The current version of the API and documentation is built for the latest API version V4. If you use an older version of this API, some endpoints or fields might be missing. New API versions are released when new functionality or bugfixes demands breaking changes to an endpoint.
We recommend everyone use API versions that are considered “under maintenance“. It is advised to update your integrations to the latest API release whenever you need new functionality, or whenever the API falls outside of the maintenance status.
We keep supporting all API versions until the last customer has moved away to new API releases. However, we only deliver bug fixes with the N-1 principle. This means that you can always count on our support with API questions and found issues, but you might be instructed to move your application to a new API version that is still under maintenance in case a bug is found in an End of Maintenance API version.
New API functionality that will be developed on request will only be released in the latest API endpoint version or split to a new API endpoint in case of breaking changes.
Release notes
Bugfix release
We have released a hotfix for the Billing API that affected v4 endpoints “invoices”, “customerinvoices”, and “consolidatedinvoices”.
Fixed Issue(s)
CD-204 - Billing API "Invoice" endpoint v4 has duplicated line items due to "resource rate periods"
Billing API Versions
API Version | API Release Date | Status | Notes |
|---|---|---|---|
v4 |
| Current Version | API extended with ResourceRatePeriod info for the Microsoft NCE billing model and PO numbers. |
v3 |
| Maintenance | |
v2 |
| End of Maintenance | API extended with new endpoints for customer invoices and subscriptionsdetails |
v1 |
| End of Life | Initial release, no longer active |
Status explanation
Status | Description | Support | BugFix releases | Feature Additions |
|---|---|---|---|---|
Current Verion | Latest API release that is fully supported, gets new features implemented to it(as long as they don't break logic) and will get bugfixes first. | Yes | Yes | Yes |
Maintenance | The API is fully supported and maintained with bugfixes when needed. | Yes | Yes | No |
End of Maintenance | The API is supported, but no new development will take place if bugs are discovered. | Yes | No | No |
End of Life | The API is no longer supported, not maintained and can be shutdown at any time | No | No | No |