asns/{id} |
GET |
Use asns route with query parameter id |
cachegroups/trimmed |
|
Use cachegroups route as trimmed is just a subset of the data returned from that endpoint |
cachegroups/{id}/unassigned_parameters |
|
Use cachegroupparameters route with query parameter cachegroup and diff that to parameters response |
cachegroups/{id} |
GET |
Use cachegroups route with query parameter id |
cdns/name/{name} |
GET |
Use cdns route with query parameter name |
cdns/{id} |
GET |
Use cdns route with query parameter id |
cdns/{name}/federations/{id} |
GET |
Use cdns/{name}/federations route with query parameter id |
deliveryservice_matches |
|
Use deliveryservices_regexes route as deliveryservice_matches is just a subset of its return data |
deliveryservices/hostname/{{host name}}/sskeys |
|
Use deliveryservices/xmlId/{{XMLID}}/sslkeys and filter the results via the hostname returned on array item |
deliveryservices/{dsid}/regexes/{regexid} |
GET |
Use deliveryservices/{dsid}/regexes route with query parameter id |
deliveryservices/{id}/unassigned_servers |
|
Use either deliveryservices/{id}/servers route and diff that with servers or even better use deliveryservices/{id}/servers/eligible/ |
deliveryservices/{id} |
GET |
Use deliveryservices route with query parameter id |
divisions/{id} |
GET |
Use divisions route with query parameter id |
keys/ping |
|
Use riak/ping route as it does the same thing and has the same backing logic |
logs/{days}/days |
|
Use logs route with query parameter days |
parameters/profile/{name} |
|
Use profiles/name/{name}/parameters route instead as same response is returned |
parameters/{id} |
GET |
Use parameters route with query parameter id |
phys_locations/trimmed |
|
Use phys_locations route as trimmed is just a subset of the data returned from that endpoint |
phys_locations/{id} |
GET |
Use phys_locations route with query parameter id |
profiles/trimmed |
|
Use profiles route as trimmed is just a subset of the data returned from that endpoint |
profiles/{id}/unassigned_parameters |
|
Use profiles/{id}/parameters route and diff that with parameters |
profiles/{id} |
GET |
Use profiles route with query parameter id |
regions/name/{name} |
GET |
Use regions route with query parameter name |
regions/{id} |
DELETE |
Use regions route with query parameter id |
regions/{id} |
GET |
Use regions route with query parameter id |
servers/hostname/{hostName}/details |
|
Use servers/details route with query parameter hostName |
servers/status |
|
Use servers route and do the counting client side. NOTE need to look into TP work to support this |
servers/{id} |
GET |
Use servers route with query parameter id |
statuses/{id} |
GET |
Use statuses route with query parameter id |
steering/{deliveryservice}/targets/{target} |
GET |
Use steering/{deliveryservice}/targets route with query parameter target |
tenants/{id} |
GET |
Use tenants route with query parameter id |
types/{id} |
GET |
Use types route with query parameter id |
user/{id}/deliveryservices/available |
|
User delivery service associations provide no value in current system |
users/{id}/deliveryservices |
|
User delivery service associations provide no value in current system |
Consider adding POSTdeliveryservices/request
to this list, as it duplicates POSTdeliveryservice_requests
.Edit: deliveryservices/request is actually for requesting that a delivery service be created and is not redundant.