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 user usage information per SKU from the Distributors resource. It is useful for distributors who want to analyze usage metrics related to specific SKUs on a given report date. For example, a distributor can retrieve usage data for a particular SKU on a specific date to monitor product adoption or performance.

Use Case Examples

  1. Fetch usage info for SKU 'ABC123' on 2023-01-01 to analyze user engagement.
  2. Retrieve all usage data for SKUs on 2023-06-30 to generate a comprehensive usage report.

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.
Date Report date in ISO8601 format, e.g., 2022-12-31.
Additional Fields Optional filters to include organizations in trial, parent organizations, and lists of MSP or organization IDs.

Output

JSON

  • data - The main response data containing usage information per SKU.
  • debug - Optional debug information including the actual URL, query parameters, headers, and body sent for each API request, useful for troubleshooting.

Dependencies

  • An API key credential for authentication with the DNSFilter API.

Troubleshooting

  • Ensure the API key is correctly set in the credentials to avoid authentication errors.
  • If pagination is enabled, verify pagination parameters to avoid incomplete data retrieval.
  • Enable debug mode to inspect the actual request and response details for troubleshooting.
  • Check the date format is ISO8601 (e.g., 2022-12-31) to prevent request validation errors.

Links

Discussion