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 a preview of a scheduled report by its ID. It is useful for users who want to fetch and view the details of a specific scheduled report preview, for example, to verify report content before distribution or further processing.

Use Case Examples

  1. Fetch a scheduled report preview by providing its unique ID to review the report details.
  2. Use this node to automate the retrieval of scheduled report previews for monitoring or integration with other systems.

Properties

Name Meaning
Id The unique identifier of the ScheduledReportPreview to retrieve.
Options Additional optional settings such as custom request body, headers, query filters, batching, debug mode, pagination, and timeout settings to customize the API request.

Output

JSON

  • id - The ID of the scheduled report preview.
  • scheduled_report_preview - The detailed data of the scheduled report preview returned by the API.
  • debug - Debug information including the actual URL, query parameters, headers, and body sent for the API request, included only if debug mode is enabled.

Dependencies

  • An API key credential for DNSFilter API authentication.

Troubleshooting

  • Ensure the provided ScheduledReportPreview ID is valid and exists in the DNSFilter system.
  • Check API key credentials and permissions to access scheduled report previews.
  • If the node returns rate limit errors, adjust batching and interval settings to avoid hitting API limits.
  • Enable debug mode to get detailed request and response information for troubleshooting.

Links

Discussion