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 performs a bulk update of domain notes for a specified resource (policies, msps, or organizations) identified by an ID. It allows updating multiple domain notes in one request, with options to append or replace existing notes, specify organization IDs, apply a single note to all domains, and set the type of list (allow or block). This is useful for managing domain notes efficiently in bulk, such as updating notes for multiple domains associated with a policy or organization.

Use Case Examples

  1. Bulk update notes for multiple domains under a specific policy ID, appending new notes to existing ones.
  2. Replace all notes for a set of domains under an MSP resource with a single note applied to all domains.

Properties

Name Meaning
Id Resource ID to update notes for.
Resource Type of resource the notes belong to (policies, msps, or organizations).
Notes Array of objects containing domain and note information to update, e.g., [{domain: 'google.com', note: 'google notes'}].
Additional Fields Optional fields to control update behavior and metadata.

Output

JSON

  • json - Response from the bulk update API call, typically the updated domain notes or status.

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 the notes JSON array is correctly formatted with domain and note fields.
  • Check API rate limits and handle 429 status responses by respecting Retry-After headers.
  • Enable debug option to see the full request and response details for troubleshooting.

Links

Discussion