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 query logs from traffic reports. It is designed to fetch raw query log data within a specified time range and with various filtering options. This node is useful for network administrators and security analysts who want to analyze DNS traffic, monitor user activity, or investigate security incidents by querying detailed logs of DNS requests.

Use Case Examples

  1. Retrieve all DNS query logs for a specific organization within the last 24 hours.
  2. Filter query logs by user agent UUIDs and domain names to analyze specific traffic sources.
  3. Fetch paginated query logs with custom filters such as application categories, MAC addresses, and IP ranges.

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 Collection of optional filters to refine the query logs request, including agent IDs, application category IDs, domain filters, time range, network IDs, user IDs, and more.

Output

JSON

  • json - The JSON response from the DNSFilter API containing the query logs data
  • debug - Optional debug information including the actual URL, query parameters, headers, and body sent for each API request, useful for troubleshooting

Dependencies

  • An API key credential for DNSFilter API authentication

Troubleshooting

  • Ensure the API key is valid and has the necessary permissions to access traffic reports.
  • Check the date and time formats for the 'From' and 'To' fields; they must be in ISO 8601 format (e.g., YYYY-MM-DDThh:mm:ss or YYYY-MM-DDThh:mm:ssZ).
  • If pagination is enabled, verify the pagination parameters and ensure the API supports the requested pagination mode.
  • If the node returns an error, check the debug output (if enabled) to see the actual request details and error messages from the API.
  • Network connectivity issues or rate limiting by the DNSFilter API can cause request failures; ensure network access and handle rate limits appropriately.

Links

Discussion