CHORUS Announces API Versioning

We are marking an important change to our API development by introducing API versioning. This change sets the foundation for scaling and evolving the development of our APIs.

API naming conventions will follow standard protocols for version controls with minor updates recorded as 1.1, 1.2 and major updates recorded as 1.0, 2.0, 3.0. Minor updates will be backwards compatible, however, major updates will not.

What this mean for you?

You will have access to earlier versions of API updates for 90-days. This will provide time to make necessary adjustments, if needed, before we deprecate and stop supporting the earlier version.

All API documentation will be updated to reflect the changes in each version and our contacts will be sent change notifications.

If you have any questions about our APIs please contact us at

Share this: