Versionning
Versioning is a crucial aspect of One Record API's design, allowing to continuously improve and add features without disrupting existing integrations. This section provides guidance on how to use One Record API versioning, ensuring a seamless integration and upgrade experience.
API Versioning
API versions are structured as follows
<apiUrl>
: The root URL of the API.<version>
: (optional) The specific version of the API, denoted as e.g.v1
,v2
, etc.<resource>
: The particular accessed resource.
Default Behavior
When no version is explicitly specified in the API request URL, the API defaults to the stable version. This ensures to automatically benefit from the recent, thoroughly tested features and performance improvements.
Version Support
One Record API maintains the following version categories:
The latest version includes beta or preview features not yet available in the stable version.
Opting for the latest version provides early access to new features, allowing to explore and integrate cutting-edge functionalities into applications.
To be noted that the latest version may not be as reliable as the stable versions, and is best used for testing and development purposes.
Current Version Information
This means that all features in the latest version have achieved the stability and reliability required for production use. There are currently no deprecated versions of our API.
Last updated