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 performs bulk updates on user agents in the DNSFilter system. It allows users to specify various filters and criteria to select user agents and apply a changeset to them in bulk. This is useful for managing large numbers of user agents efficiently, such as updating their policies, states, or other attributes in one operation.

Use Case Examples

  1. Updating the policy for all user agents in a specific organization.
  2. Changing the agent state for user agents that have received traffic in the last 15 minutes.
  3. Applying a changeset to user agents filtered by tags and release channels.

Properties

Name Meaning
Additional Fields Optional filters and parameters to specify which user agents to update and how, including agent state, version, block page ID, name search, network IDs, organization IDs, policy ID, policy schedule, release channels, scheduled policy ID, search keywords, state, status, tags, traffic received in last 15 minutes, type, IDs to include or exclude, and the changeset to apply.

Output

JSON

  • json - The JSON response from the DNSFilter API representing the result of the bulk update operation.

Dependencies

  • An API key credential for DNSFilter API authentication

Troubleshooting

  • Ensure the API key credential is correctly configured and has the necessary permissions to perform bulk updates.
  • Verify that the IDs or filters used to select user agents are valid and correspond to existing user agents in the DNSFilter system.
  • Check for rate limiting errors (HTTP 429) and use batching options to avoid hitting rate limits.
  • If the node throws errors, enable the debug option to see the actual request URL, headers, query parameters, and body for troubleshooting.

Links

Discussion