Introduction
Synerise RESTful APIs are a quick and simple way to integrate your existing or future systems with Synerise or benefit from functionalities available within your applications.
SSL
Synerise API requires connectivity over HTTPS (SSL) and supports the TLS 1.2 protocol (support for newer versions to be added in the near future).
Servers
When working with the Synerise API, make sure you’re using the correct base URL, depending on the cloud where your workspace is hosted:
https://api.synerise.comfor Microsoft Azurehttps://api.geb.synerise.comfor Google Cloud Platform
API Versioning
Synerise is built with CI/CD (Continuous Integration/Continuous Delivery) principles in mind and we often deploy changes multiple times a day.
We do not have fixed release cycles, but instead features are brought live for you as soon as they are ready.
Such an approach allows us to deliver features, changes, and bug fixes very fast and keeping track of them is possible thanks to our live changelog.
Thus, as part of our API Contract, we want to ensure that within an API Version:
- No fields will be deleted or changed in a non-backwards compatible way.
- We make changes that are additional, such as new fields, new methods, new error messages/codes, or mandatory parameters becoming optional (but, generally speaking, not causing compatibility issues).
Whenever we may need to roll out elements that are not backwards compatible, we will do that as a new API version for the given functional area, so an endpoint that was version 1 is now also available as version 2, with the previous one still being operational.
Deprecation
Endpoints that already have newer versions send X-API-DEPRECATED in the response Headers, giving you time to switch to the new endpoint.
Deprecated API endpoints are also marked visually in the API reference pages.
