Network Edge - Feb 2021 API Release Notes

Release: Feb 2021.1

Feature	Summary of Release
Endpoint Changes (update)	In this release, we are changing several endpoints to have a consistent naming convention. Below is a list of all the changes, the old endpoints followed by the new ones. /v1/services/vpn to /v1/vpn /v1/services/vpn/{uuid} to /v1/vpn/{uuid} /v1/services/bgp to /v1/bgp /v1/services/bgp/{uuid} to /v1/bgp/{uuid} /v1/device/type to /v1/deviceTypes /v1/device/license/{uuid} to /v1/devices/{uuid}/licenseTokens /v1/device/license/file to /v1/devices/licenseFiles /v1/device/license/file/{uuid} to /v1/devices/{uuid}/licenseFiles /v1/device/ac-template to /v1/aclTemplate /v1/device/acl-template/{uuid} to /v1/aclTemplates/{uuid} /v1/device/additionalBandwidth/{uuid} to /v1/devices/{uuid}/additionalBandwidths /v1/device/dns-lookup to /v1/dnsLookup /v1/device/ping/{uuid} to /v1/devices/{uuid}/ping /v1/service/ssh-user to /v1/sshUsers /v1/services/ssh-user/{uuid} to /v1/sshUsers/{uuid} /v1/services/ssh-user/{uuid}/association to /v1/sshUsers/{sshUserUuid}/devices/{deviceUuid} /v1/device/account/{metro} to /v1/accounts/{metro} /v1/device/agreement to /v1/agreements/accounts /v1/device/agreement/order to /v1/agreements/orders /v1/device/agreement/status to /v1/agreeements/accounts /v1/device/agreement/vendor to /v1/agreements/vendors /v1/device/order-summary to /v1/orderSummaries /v1/device/price to /v1/prices /v1/device/link to /v1/links /v1/device/link/{uuid} to /v1/links/{uuid}
Field Name Changes (update)	Here's a list of all the field name changes we are making this time, the old followed by the new. virtualDeviceUUID to virtualDeviceUuid redundantUUID to redundantUuid secondaryUUID to secondaryUuid referenceID to referenceId termsVersionID to termsVersionId
Clustering Changes (update)	We have changed the structure of cluster details object, both the payload to create clusters and the GET response for a cluster device. This was done primarily to accomodate creation of Palo Alto, Fortinet, and Velocloud SDWAN clusters. Check out Launch Cluster Device and Get Device Types for more details.

Feature

Summary of Release

Endpoint Changes
(update)

In this release, we are changing several endpoints to have a consistent naming convention. Below is a list of all the changes, the old endpoints followed by the new ones.

/v1/services/vpn to /v1/vpn
/v1/services/vpn/{uuid} to /v1/vpn/{uuid}
/v1/services/bgp to /v1/bgp
/v1/services/bgp/{uuid} to /v1/bgp/{uuid}
/v1/device/type to /v1/deviceTypes
/v1/device/license/{uuid} to /v1/devices/{uuid}/licenseTokens
/v1/device/license/file to /v1/devices/licenseFiles
/v1/device/license/file/{uuid} to /v1/devices/{uuid}/licenseFiles
/v1/device/ac-template to /v1/aclTemplate
/v1/device/acl-template/{uuid} to /v1/aclTemplates/{uuid}
/v1/device/additionalBandwidth/{uuid} to /v1/devices/{uuid}/additionalBandwidths
/v1/device/dns-lookup to /v1/dnsLookup
/v1/device/ping/{uuid} to /v1/devices/{uuid}/ping
/v1/service/ssh-user to /v1/sshUsers
/v1/services/ssh-user/{uuid} to /v1/sshUsers/{uuid}
/v1/services/ssh-user/{uuid}/association to /v1/sshUsers/{sshUserUuid}/devices/{deviceUuid}
/v1/device/account/{metro} to /v1/accounts/{metro}
/v1/device/agreement to /v1/agreements/accounts
/v1/device/agreement/order to /v1/agreements/orders
/v1/device/agreement/status to /v1/agreeements/accounts
/v1/device/agreement/vendor to /v1/agreements/vendors
/v1/device/order-summary to /v1/orderSummaries
/v1/device/price to /v1/prices
/v1/device/link to /v1/links
/v1/device/link/{uuid} to /v1/links/{uuid}

Field Name Changes
(update)

Here's a list of all the field name changes we are making this time, the old followed by the new.

virtualDeviceUUID to virtualDeviceUuid
redundantUUID to redundantUuid
secondaryUUID to secondaryUuid
referenceID to referenceId
termsVersionID to termsVersionId

Clustering Changes
(update)

We have changed the structure of cluster details object, both the payload to create clusters and the GET response for a cluster device. This was done primarily to accomodate creation of Palo Alto, Fortinet, and Velocloud SDWAN clusters. Check out Launch Cluster Device and Get Device Types for more details.