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 allows users to bulk add one or more domains to the allow list of one or more policies in the DNSFilter system. It is useful for administrators who need to efficiently update multiple policies with allowed domains in a single API call, saving time and reducing manual effort. For example, a security admin can add trusted domains to multiple policies at once to ensure they are not blocked by DNS filtering.

Use Case Examples

  1. Bulk add multiple trusted domains to several policies to allow access across an organization.
  2. Add a list of domains to the allow list of specific policies to customize network filtering behavior.

Properties

Name Meaning
Domains List of domains to add to the allow list of policies.
Notes Optional notes associated with each domain.
Policy Ids List of policy IDs to which the domains will be added.

Output

JSON

  • debug - Debug information including URL, query parameters, headers, and body sent for the API request (if debug option is enabled).
  • response - Response from the API after adding domains to the allow list.

Dependencies

  • An API key credential for DNSFilter to authenticate API requests.

Troubleshooting

  • Ensure the API key credential is correctly configured and has the necessary permissions.
  • Verify that the policy IDs and domains provided are valid and exist in the DNSFilter system.
  • If rate limiting errors occur (HTTP 429), consider using batching options to space out requests.
  • Enable debug option to get detailed request and response information for troubleshooting.

Links

Discussion