GET /radar/traffic_anomalies/locations

Retrieves the sum of Internet traffic anomalies, grouped by location. These anomalies are signals that might indicate an outage, automatically detected by Radar and manually verified by our team.

Servers

Query parameters

Name Type Required Description
limit Integer No

Limits the number of objects returned in the response.

Default value: 5

format String No

Format in which results will be returned.

Valid values:

  • "CSV"
  • "JSON"
dateEnd String No

End of the date range (inclusive). Alternative to dateRange; provide together with dateStart.

dateStart String No

Start of the date range (inclusive). Alternative to dateRange; provide together with dateEnd.

status String No

Valid values:

  • "VERIFIED"
  • "UNVERIFIED"
dateRange String No

Filters results by a relative date range ending at the current time. Use <n>d for days (up to 364d) or <n>w for weeks (up to 52w), e.g. 7d. Append control to request the equivalent previous period for comparison: the comparison window is shifted back by the current window's length rounded up to a whole number of weeks, so it keeps the same weekday alignment and does not overlap the current window (e.g. 3dcontrol covers days -10 to -7, 7dcontrol covers days -14 to -7, 28dcontrol covers days -56 to -28, and 10dcontrol covers days -24 to -14). Mutually exclusive with dateStart/dateEnd.

How to start integrating

  1. Add HTTP Task to your workflow definition.
  2. Search for the API you want to integrate with and click on the name.
    • This loads the API reference documentation and prepares the Http request settings.
  3. Click Test request to test run your request to the API and see the API's response.