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 deletion of domains from the block list of one or more policies in the DNSFilter system. It is useful for administrators who need to efficiently manage and update multiple policies by removing multiple blocklist domains in a single operation. For example, if a set of domains are no longer considered harmful or need to be unblocked across several policies, this node can be used to remove them all at once.

Use Case Examples

  1. Remove multiple domains from the blocklist of selected policies to allow access to previously blocked websites.
  2. Clean up outdated or incorrect blocklist entries across multiple policies in bulk.

Properties

Name Meaning
Additional Fields Optional fields to specify domains, notes, and policy IDs for the bulk delete operation.
Options Additional request options such as custom body, headers, query filters, batching, debug, pagination, and timeout settings.

Output

JSON

  • json - The JSON response from the DNSFilter API for the bulk delete blocklist domains 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 delete operations on policies.
  • Check that the domains and policy IDs provided are valid and exist in the DNSFilter system.
  • If rate limiting errors occur, adjust batching and batch interval options to reduce request frequency.
  • Enable debug option to see detailed request and response information for troubleshooting.

Links

Discussion