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 manage policies, specifically to remove a single domain from a policy's blocklist. It is useful for network administrators or security teams who want to update DNS filtering policies by removing domains from the blocklist to allow access. For example, if a domain was mistakenly blocked, this operation can be used to remove it from the blocklist of a specified policy.

Use Case Examples

  1. Remove 'example.com' from the blocklist of policy ID 123 with a note explaining the reason.
  2. Automate the removal of multiple domains from blocklists across different policies by iterating over input items.

Properties

Name Meaning
Id The unique identifier of the policy from which the block domain will be removed.
Domain The domain name to be removed from the blocklist of the specified policy.
Note A note or reason for removing the domain from the blocklist, providing context for the change.
Additional Fields Optional parameters such as whether to include relationships in the response.
Options Additional request options like custom body, headers, query filters, batching, debug, pagination, and timeout settings.

Output

JSON

  • json - The JSON response from the DNSFilter API after removing the block domain from the specified policy.

Dependencies

  • DNSFilter API key credential

Troubleshooting

  • Ensure the policy ID and domain are correct and exist in the DNSFilter system.
  • Check that the API key credential is valid and has permissions to modify policies.
  • If rate limiting errors occur, use batching and interval options to throttle requests.
  • Enable debug option to see the full request and response details for troubleshooting.

Links

Discussion