Get the list of IPv4 and IPv6 prefixes of the Datacenter given.

GET {{baseUrl}}/v1/datacenter/:datacenter_id/prefixes

What

Obtain the full list of IPv4 and IPv6 prefixes of the Datacenter passed as a parameter.

Parameters

The endpoint accepts only the following parameter in the path: - datacenter_id: (Mandatory) The internal Datacenter ID to be queried.

Result

The result is a JSON object with the following structure: - self: the URI of the API call - datacenter_id: the URI to query the full details of the Datacenter. - prefixes_v4: the list of IPv4 prefixes that belong to the Datacenter. Each element of the list is a JSON object with the following structure:

- ``self``: the URI to individual IPv4 prefix.
- ``datacenter_id``: the URI to query the full details of the Datacenter.
- ``score``: The risk score of the prefix. It ranges from 0 to 99.
- ``risk``: The risk of the prefix. The allowed values are: LOW, MEDIUM, HIGH. It's a human readable representation of the score.
- ``min_score``: The minimum risk score of the prefix. It ranges from 0 to 99.
- ``max_score``: The maximum risk score of the prefix. It ranges from 0 to 99.
- ``ip_abuse_total``: The total number of IPs that have been reported as abuse in the range.
  • prefixes_v6: the list of IPv6 prefixes that belong to the Datacenter. Each element of the list is a JSON object with the following structure:

    • self: the URI to individual IPv4 prefix.
    • datacenter_id: the URI to query the full details of the Datacenter.
    • score: The risk score of the prefix. It ranges from 0 to 99.
    • risk: The risk of the prefix. The allowed values are: LOW, MEDIUM, HIGH. It's a human readable representation of the score.
    • min_score: The minimum risk score of the prefix. It ranges from 0 to 99.
    • max_score: The maximum risk score of the prefix. It ranges from 0 to 99.
    • ip_abuse_total: The total number of IPs that have been reported as abuse in the range.

Errors

The endpoint will return the following errors: - a 404 Not Found error if the Datacenter was not found. - a 422 Unprocessable Entity error if the Datacenter number is malformed.

It will also return the API Global errors described in the API description.

HEADERS

KeyDatatypeRequiredDescription
Acceptstring

RESPONSES

status: OK

{"self":"dolor","prefixes_v4":[{"datacenter":"quis minim ut labore","self":"dolor exercitation dolore reprehenderit adipisicing","min_score":0,"max_score":0,"ip_abuse_total":0,"score":-75774131,"risk":"UNKNOWN"},{"datacenter":"voluptate consequat elit","self":"ex deserunt si","min_score":0,"max_score":0,"ip_abuse_total":0,"score":-21373312,"risk":"UNKNOWN"}],"prefixes_v6":[{"datacenter":"ex","self":"incididunt irure veniam","min_score":0,"max_score":0,"ip_abuse_total":0,"score":-35530305,"risk":"HIGH"},{"datacenter":"qui in consectetur mollit","self":"aute i","min_score":0,"max_score":0,"ip_abuse_total":0,"score":74129977,"risk":"HIGH"}]}