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 fetches traffic report data specifically related to domain requests grouped by collections from the DNSFilter API. It is useful for analyzing network traffic patterns, security threats, and usage statistics by domain within different collections over specified time periods. For example, a network administrator can use this node to monitor domain request volumes and security reports for various collections in their organization, helping to identify potential threats or usage trends.

Use Case Examples

  1. Retrieve total domain requests grouped by collections for the last 7 days to analyze traffic patterns.
  2. Fetch domain request data filtered by specific agent IDs and application IDs to monitor usage and security threats within certain 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 domain requests collections report, such as agent IDs, application IDs, bucket size, category IDs, collection IDs, domain prefix, date range, MAC addresses, network IDs, organization IDs, private IP ranges, security report flag, grouping by individual collections, traffic source, report end date, report type, and user IDs.

Output

JSON

  • json - API response data containing domain requests grouped by collections and related traffic report information

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 report endpoints.
  • Check the date and time formats 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 'Additional Fields' filters for correct data types and valid values to prevent API errors.

Links

Discussion