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 operation checks whether the selected user agents have mixed values for their attributes. It is useful for scenarios where you want to verify if user agents in bulk have inconsistent or varying attribute values, such as different states, versions, or tags. For example, it can be used to identify if a group of user agents have mixed online/offline states or different policy assignments.

Use Case Examples

  1. Check if a set of user agents have mixed online/offline states.
  2. Verify if user agents have mixed policy assignments before applying bulk updates.

Properties

Name Meaning
Agent State Filter user agents by their agent state (e.g., protected, unprotected, bypassed, uninstalled).
Name Search A search term to filter user agents by client name fields such as hostname or friendly name.
Network Ids Filter user agents by network IDs; defaults to all if not specified.
Organization Ids Filter user agents by organization IDs; defaults to the user's organization ID if not specified.
Search Filter user agents by keyword(s) such as hostname or friendly name.
State Filter user agents by their online/offline state.
Status Filter user agents by status attributes such as active, disabled, or uninstalled.
Tags Filter user agents by tags.
Traffic Received Last 15 Mins Filter user agents that have received traffic in the last 15 minutes.
Type Filter user agents by type, defaulting to non-proxy/no-relays user agents.
Ids IDs of user agents to use in the check.

Output

JSON

  • mixed - Indicates whether the selected user agents have mixed attribute values.
  • details - Details about which attributes are mixed among the user agents.

Dependencies

  • An API key credential for authentication with the DNSFilter API.

Troubleshooting

  • Ensure the API key credential is correctly configured and has the necessary permissions.
  • Verify that the input user agent IDs or filters are valid and correctly formatted.
  • Check for rate limiting errors (HTTP 429) and use batching options to avoid hitting limits.
  • Enable debug mode to see the actual request URL, headers, query parameters, and body for troubleshooting.

Links

Discussion