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 by collections over a specified period. It is useful for network administrators or analysts who want to monitor and analyze application usage patterns within different collections in their network environment. For example, it can be used to generate reports on how many requests were made by various applications grouped by collections, filtered by parameters such as agent IDs, application categories, date ranges, and more.

Use Case Examples

  1. Generate a report of total application requests by collections for the last 24 hours.
  2. Filter application request statistics by specific user agent types and application categories within collections.

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, agent types, application category IDs, application IDs, collection IDs, date range (from/to), MAC addresses, user names, NAT IPs, network IDs, organization IDs, private IP ranges, security report flag, source type, report type, and user IDs.

Output

JSON

  • json - The JSON response from the DNSFilter API containing the application requests statistics by collections.

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.
  • Check the date and time format for 'from' and 'to' fields to match the expected ISO8601 format.
  • If pagination is enabled, verify pagination settings to avoid incomplete data retrieval.
  • Review the debug output (if enabled) for the actual request URL, headers, and body to troubleshoot request issues.

Links

Discussion