1.7 Versioning and Capability Negotiation

This protocol supports versioning. Currently 4 versions are supported: v1, v2, v3, and v4.<1> The URL has to include the v1, v2, v3, or v4 token. Each API that supports additional properties in version n compared to n-1 will be contained in a description of the behavior in the sections following Protocol Details (section 3).

The 4 prefixes supported are as follows:

 https://<url>/networking/v1/
  
 https://<url>/networking/v2/
  
 https://<url>/networking/v3/
  
 https://<url>/networking/v4/

url: The address or name of the REST server of the Network Controller. 

This protocol provides a mechanism for capability negotiation.<2>

The JSON Schemas in the appendix are present for a given version only if there are changes compared to its previous version. For example, accessControlLists resources can be retrieved via v2 and v3 uri in the current version, but there are no changes in properties compared to v1. In such a case, only the v1 schema is documented.