GET /radar/bgp/leaks/events

Retrieves the BGP route leak events.

Servers

Query parameters

Name Type Required Description
page Integer No

Current page number, starting from 1.

Default value: 1

sortOrder String No

Sort order.

Valid values:

  • "DESC"
  • "ASC"
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.

involvedCountry String No

Country code of a involved ASN in a route leak event.

sortBy String No

Sorts results by the specified field.

Valid values:

  • "PREFIXES"
  • "ID"
  • "TIME"
  • "PEERS"
  • "ORIGINS"
  • "LEAKS"
per_page Integer No

Number of entries per page.

Default value: 50

dateStart String No

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

leakAsn Integer No

The leaking AS of a route leak event.

eventId Integer No

The unique identifier of a event.

involvedAsn Integer No

ASN that is causing or affected by a route leak event.

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.