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 adds a single domain to the allowlist of a specified policy in the DNSFilter system. It is useful for scenarios where you want to explicitly permit access to a domain within a policy's filtering rules, such as allowing a trusted partner's domain or a necessary service domain that might otherwise be blocked.

Use Case Examples

  1. Allowing 'example.com' domain in a policy with ID 123 to ensure it is accessible despite other filtering rules.
  2. Adding a domain to the allowlist to prevent it from being blocked by DNS filtering policies.

Properties

Name Meaning
Id The unique identifier of the policy to which the domain will be added.
Domain The domain name to be added to the allowlist of the policy.
Note A note or comment explaining the reason or context for adding the domain to the allowlist.
Additional Fields Optional parameters to include in the request, such as whether to include relationships in the response.

Output

JSON

  • json - The JSON response from the API call, typically including details of the updated policy or confirmation of the domain addition.

Dependencies

  • An API key credential for DNSFilter to authenticate requests.

Troubleshooting

  • Ensure the policy ID is valid and exists in the DNSFilter system.
  • Verify the domain format is correct and allowed by the API.
  • Check API key credentials and permissions to modify policies.
  • If rate limited, respect the Retry-After header and retry after the specified time.

Links

Discussion