ThousandEyes API License Terms and Support Policy
Use & Access of the ThousandEyes API
Use of this ThousandEyes Developer Reference is governed by the Cisco DevNet Terms of Service (the “ToS”). Use and access of the associated ThousandEyes API is governed by Cisco General Terms (the “General Terms”). You may only use the ThousandEyes API if You have a valid Use Right to use ThousandEyes. The following additional terms supplement the Cisco ToS and General Terms. Defined terms will have the same meaning as stated in the Cisco ToS and/or General Terms, unless defined below. If the terms below conflict with the Cisco ToS and/or General Terms, the terms below will control.
ThousandEyes may modify (i) access to and/or how the ThousandEyes API functions, (ii) our policies related to use and/or access of the ThousandEyes API, and (iii) the Documentation that we make publicly available describing the ThousandEyes API, from time to time without advance notice (each a “Modification”). ThousandEyes will use commercially reasonable efforts to notify You of any Modifications.
ThousandEyes will update the ThousandEyes API version if the structure of the ThousandEyes API output substantively changes, format is modified, or code is deprecated.
ThousandEyes API Version Support Notice
ThousandEyes only supports the (i) most recent major release of the ThousandEyes API, and (ii) prior major version of the ThousandEyes API for a period of 12-months after the 90-day transition period described below.
Transition to New Versions
When a new major release reaches General Availability (GA), the prior version remains the default for 90-days. After this 90-day period, the most recent release becomes the default version. The 12-month support window for the prior version begins once it is no longer the default.
Unsupported Versions
Requests made to unsupported versions of the ThousandEyes API will return an error response.
Unversioned Requests
API v6 is the final version to support unversioned requests. All subsequent versions require the version to be explicitly specified in the request path (for example, /v7/).