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 retrieve information about policy IPs. Specifically, for the 'PolicyIPs' resource and 'Get' operation, it fetches user-associated policy IPs or details of a specific policy IP by ID. It supports fetching all results with pagination or a single page of results. This node is useful for scenarios where users need to manage or audit IP addresses associated with policies in DNSFilter, such as retrieving all policy IPs for an organization or getting details of a particular policy IP.

Use Case Examples

  1. Retrieve all policy IPs associated with a user or organization.
  2. Get detailed information about a specific policy IP by its ID.

Properties

Name Meaning
Return All Whether to return all results or only a single page. When disabled, no pagination parameters are sent and only one page of results is returned.
Id The ID of the specific policy IP to retrieve (used when fetching a single policy IP). This is required for the 'show' operation.

Output

JSON

  • id - The unique identifier of the policy IP.
  • ip_address - The IP address associated with the policy.
  • policy_id - The ID of the policy to which the IP belongs.
  • created_at - Timestamp when the policy IP was created.
  • updated_at - Timestamp when the policy IP was last updated.

Dependencies

  • An API key credential for DNSFilter to authenticate requests.

Troubleshooting

  • Ensure the API key is valid and has the necessary permissions to access policy IPs.
  • Check network connectivity to the DNSFilter API endpoint.
  • If pagination is enabled, verify that pagination parameters are correctly set to avoid incomplete data.
  • Common errors include 401 Unauthorized (invalid API key) and 429 Too Many Requests (rate limiting). Handle these by verifying credentials and implementing retry logic with delays.

Links

Discussion