Skip to main content
Skip table of contents

Versioning NEW

The current version of the API and documentation is built for the latest API version V1. New API versions are released when new functionality or bug fixes 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.

Billing API Versions

API Version

API Release date

Status

Notes

v1

November 2023

Current version

Status explanation

Status

Description

Support

Bugfix Releases

Feature Additions

Current Version

Latest API release that is fully supported, gets new features implemented to it (as long as they don't break logic) and will get bug fixes first.

Yes

Yes

Yes

Maintenance

The API is fully supported and maintained with bug fixes 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

Release notes

  • There was an issue with list items in the XML response of the Billing API. The child tag would have the same name as the parent.
    For Example:

CODE
<Invoices>
	<Invoices>
	</Invoices>
</Invoices>

We've fixed this issue so the child element is now in the singular form:

CODE
<Invoices>
	<Invoice>
	</Invoice>
</Invoices>

Tags which have been renamed: Invoices -> Invoice, Customers -> Customer, Subscriptions -> Subscription, PriceLines -> Line.

Known Issues and limitation

The following issues and limitations are reported to our team and are currently under review, in our backlog, or in development, and will be implemented in future versions.

Did you find an issue, or require functionality that is not listed in the above table? Please contact our support team to submit your request.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.