DNSFilter icon

DNSFilter

**Note:** If you are a distributor integrating with DNSFilter, please check out our [Distributors Development Guide](/docs/distributors).### Authentication- Authentication is required for most, but not all, endpoints.- Authentication is done by setting the `Authorization` request header. The header value is the API key itself. For example: `Authorization: eyJ...`- An API key can be obtained through the DNSFilter dashboard under Account Settings. For additional information see [this KB article](https://help.dnsfilter.com/hc/en-us/articles/21169189058323-API-Tokens).### Rate Limiting- All endpoints are rate limited.- The limits may vary by endpoint, but are generally consistent.- When the rate limit is exceeded the API will return the standard `429` HTTP status.- The following headers will also be provided in the response: `Retry-After`, `RateLimit-Policy`, `RateLimit`, `RateLimit-Limit`, `RateLimit-Remaining`, `RateLimit-Reset`. For details on the values of these headers, see the following articles [here](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Retry-After), [here](https://www.ietf.org/archive/id/draft-ietf-httpapi-ratelimit-headers-08.html), and [here](https://www.ietf.org/archive/id/draft-polli-ratelimit-headers-05.html).- For additional information see [this KB article](https://help.dnsfilter.com/hc/en-us/articles/38202811088403-API-Rate-Limits).### Error Handling- The API uses standard HTTP status codes to indicate success or failure.- For _V1_ endpoints the response format is: ```json { "error": "string", "type": "string(optional)" } ```- For _V2_ endpoints the response format is: ```json { "error": { "message": "string", "type": "string(optional)" } } ```### PaginationFor the _V1_ endpoints, the pagination parameters are nested. That is to say,if passed as JSON they look like this: `{"page[number]": 1, "page[size]": 10}`.To pass this information in the URL query string, it would be formatted likethis: `...?page%5Bnumber%5D=1&page%5Bsize%5D=10`.In this guide, the UI will indicate that `page` is an `object` and if youwant to set values when trying the request, you must enter it as if it wasthe JSON above.### A Quick ExampleThe following will return information about the currentlyauthenticated user.```bash% curl -H 'Authorization: ***' https://api.dnsfilter.com/v1/users/self{ "data": { "id": "12345", "type": "users", "attributes": { "name": "John Doe", "email": "john@example.com", ...additional fields...}}}```

Actions328

Overview

This node interacts with the DNSFilter API to retrieve traffic report data specifically for the 'Top networks' operation under the 'TrafficReports' resource. It allows users to fetch the top networks in a specified period, with various filtering options such as agent IDs, application IDs, date ranges, MAC addresses, network IDs, organization IDs, and more. The node supports pagination and can return either all results or a single page of results. It is useful for analyzing network traffic patterns and identifying the most active or significant networks within an organization or set of organizations.

Use Case Examples

  1. A network administrator wants to get the top networks by traffic volume for the last 24 hours to analyze network usage patterns.
  2. A security analyst needs to filter top networks that have reported threats within a specific date range to investigate potential security incidents.

Properties

Name Meaning
Return All Whether to return all results or only a single page. When disabled, no pagination parameters are sent and only one page of results is returned.
Additional Fields Optional filters and parameters to refine the traffic report query, including agent IDs, application IDs, date range, MAC addresses, network IDs, organization IDs, pagination, security report flag, traffic source, and report type.

Output

JSON

  • json - The JSON response from the DNSFilter API containing the top networks traffic report data.

Dependencies

  • An API key credential for DNSFilter API authentication

Troubleshooting

  • Ensure the API key credential is correctly configured and has the necessary permissions to access traffic reports.
  • Verify that the date and time formats for 'From' and 'To' fields are correct and in ISO 8601 format.
  • Check the network and organization IDs provided in the filters are valid and accessible by the API key.
  • If pagination is enabled, ensure the pagination parameters are correctly set to avoid incomplete data retrieval.
  • Enable debug mode to see the actual API request details if encountering unexpected errors or empty responses.

Links

Discussion