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 fetches covered users information by organization for a specified date range from the Distributors resource in the DNSFilter API. It is useful for distributors who need to generate reports on user coverage within organizations over a given period, with options to include trial organizations, parent organizations, and filter by MSP or organization IDs. For example, a distributor can use this operation to analyze user coverage trends from December 1 to December 31, 2022, including trial organizations and parent MSP organizations.

Use Case Examples

  1. Fetch covered users summary by organization for December 2022, including trial organizations and parent MSP organizations.
  2. Generate a report of covered users for specific MSP IDs and organization IDs within a date range.

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.
From Report range lower limit. Date in ISO8601 format, e.g.: 2022-12-01.
To Report range upper limit. Date in ISO8601 format, e.g.: 2022-12-31.
Additional Fields Optional filters and flags to include trial organizations, parent organizations, and filter by MSP or organization IDs.

Output

JSON

  • data - The API response data containing covered users summary by organization.

Dependencies

  • An API key credential for DNSFilter API authentication.

Troubleshooting

  • Ensure the date range does not exceed the maximum allowed 31 days to avoid API errors.
  • Verify that the API key credential is correctly configured and has read-only access for this endpoint.
  • If pagination is enabled, check pagination settings to retrieve all pages of results.
  • Enable debug option to see the actual request details if the API call fails for troubleshooting.

Links

Discussion