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 statistics specifically related to application requests over a specified period. It supports fetching detailed statistics about the number of requests by application, filtered by various parameters such as agent IDs, application categories, organizations, networks, and time ranges. This node is useful for network administrators and security analysts who want to monitor application usage and traffic patterns within their network environment.

Use Case Examples

  1. A network administrator wants to analyze the total number of requests made by different applications in the last 24 hours to identify the most used applications.
  2. A security analyst needs to filter application request statistics by specific user agents and organizations to investigate unusual traffic patterns.

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 category IDs, application IDs, collection IDs, date range (from/to), MAC addresses, MSP ID, application name filter, NAT IPs, network IDs, organization IDs, private IP range, security report flag, traffic source, and report type.
Options Additional request options such as custom body, custom headers, query filters, batching settings, debug mode, pagination settings, and timeout configuration.

Output

JSON

  • json - The JSON response from the DNSFilter API containing application request statistics and related data.

Dependencies

  • DNSFilter API key credential

Troubleshooting

  • Ensure the DNSFilter API key credential is correctly configured and has the necessary permissions to access traffic report endpoints.
  • Check the date and time formats for 'from' and 'to' fields to match the expected ISO8601 format (YYYY-MM-DDThh:mm:ss or YYYY-MM-DDThh:mm:ssZ).
  • If pagination is enabled, verify pagination settings such as page size and mode to avoid incomplete data retrieval.
  • Enable debug mode to inspect the actual API request and response details for troubleshooting errors.

Links

Discussion