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 deletes multiple domain notes in batch for a specified resource (policies, msps, or organizations) and resource ID. It is useful for bulk removal of domain notes associated with a resource, such as cleaning up or managing domain allow/block lists efficiently. For example, deleting multiple domain notes related to a policy or organization in one API call.

Use Case Examples

  1. Delete multiple domain notes for a policy with ID 123 by specifying a comma-separated list of domains to remove.
  2. Batch delete domain notes for an MSP resource by providing the MSP ID and domains to be deleted.

Properties

Name Meaning
Id The ID of the resource (policy, MSP, or organization) for which the domain notes will be deleted.
Resource The type of resource to which the domain notes belong. Valid options are policies, msps, or organizations.
Domains Comma separated list of domains whose notes will be deleted in batch.
Options Additional optional settings such as custom request body, headers, query filters, batching, debug mode, pagination, and timeout.

Output

JSON

  • json - The JSON response from the API after batch deleting domain notes.

Dependencies

  • An API key credential for DNSFilter API authentication.

Troubleshooting

  • Ensure the resource ID and resource type are valid and exist in the DNSFilter system.
  • Verify that the domains list is correctly formatted as a comma-separated string.
  • Check API rate limits and handle 429 status codes by respecting Retry-After headers.
  • Enable debug mode to see the actual request URL, headers, query parameters, and body for troubleshooting.
  • Handle API errors gracefully and check error messages returned by the DNSFilter API.

Links

Discussion