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 counts of user agent bulk updates based on various filtering criteria. It is useful for scenarios where you need to analyze or monitor the status and distribution of bulk updates applied to user agents in your network environment. For example, you can filter counts by agent state, block page ID, organization ID, policy ID, release channels, and other attributes to get detailed insights into the bulk update operations.

Use Case Examples

  1. Retrieve counts of user agent bulk updates filtered by agent state and organization ID.
  2. Get counts of bulk updates for user agents that have received traffic in the last 15 minutes.
  3. Fetch counts of user agent bulk updates filtered by policy ID and release channel.

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 counts query, such as agent state, block page ID, name search, network IDs, organization ID, policy ID, release channels, scheduled policy ID, search keywords, state, status, tags, traffic received in last 15 minutes, and user agent type.

Output

JSON

  • counts - Counts of user agent bulk updates matching the specified filters

Dependencies

  • An API key credential for DNSFilter API

Troubleshooting

  • Ensure the API key is valid and has the necessary permissions to access user agent bulk update counts.
  • Check that the filter parameters are correctly formatted and valid according to the DNSFilter API documentation.
  • If pagination is enabled, verify that pagination settings are correctly configured to avoid incomplete data retrieval.
  • Enable debug mode to see the actual API request details for troubleshooting request issues.

Links

Discussion