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 related to domains over a specified period. It supports fetching aggregated domain statistics such as total requests, threats, categories, and other domain-related metrics. Users can filter the data by domain name, FQDN, date range, MSP ID, network IDs, and organization ID. The node supports pagination and can return all results or a single page based on user preference. It is useful for network administrators and security analysts who want to monitor domain traffic and security events within their network or organization.

Use Case Examples

  1. Fetch total domain statistics for a specific domain over the last week to analyze traffic patterns.
  2. Retrieve domain threat statistics filtered by organization ID to assess security risks.
  3. Get paginated domain request statistics with custom filters for detailed reporting.

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 to refine the domain stats query, including domain prefix, FQDN substring, date range (from/to), MSP ID, network IDs, and organization ID.
Options Additional request options including custom JSON body, custom HTTP headers, query filters, batching settings, debug mode, pagination configuration, and request timeout.

Output

JSON

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

Dependencies

  • DNSFilter API key credential

Troubleshooting

  • Ensure the DNSFilter API key credential is correctly configured and has the necessary permissions.
  • Check the date format for 'From' and 'To' fields; it should be in ISO 8601 format (e.g., YYYY-MM-DDThh:mm:ss or YYYY-MM-DDThh:mm:ssZ).
  • If pagination is enabled, verify pagination parameters are correctly set to avoid incomplete data.
  • Enable debug mode to get detailed request and response information for troubleshooting API call issues.
  • Handle API rate limits by respecting Retry-After headers and implementing appropriate delays between requests.

Links

Discussion