2 Minute Read

| Versioning

75F aims to be backward compatible with previous versions of the API and to protect implementations from breaking when new features or changes are implemented. The API also strives to be self-documenting, easy to understand, and use. 

The 75F API requires an explicitly specified version number in all request URLs. This explicit API version number ensures that the caller makes requests to the appropriate version of the API and that future changes in the API do not impact the caller's code. A prime goal of the 75F API is to always be backward compatible with a specific version. 

The API version may increase if changes added to the API are no longer compatible with the previous versions of the API. This may be the structure of data objects, removal of fields, or other drastic and disruptive changes. The API version is not expected to change if new fields are added to objects. 

Note: It is the responsibility of the API consumer to ensure that the addition of fields to the JSON representation of objects is properly handled by the caller's deserialization implementation. 

| URL's

The base URL format for making API calls follows the below convention: 


The following base URLs are used to access the API: 







Note: You must use HTTPS to make API requests, HTTP is not supported and your client will be redirected to the HTTPS URL. Most HTTP client implementations do not support redirection by default if at all. 




Please sign in to leave a comment.

Was this article helpful?

0 out of 0 found this helpful
Powered by Zendesk