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 create a new scheduled policy. It is useful for automating the creation of scheduled policies that define specific time-based rules for network filtering, such as blocking or allowing certain policies during specified time blocks. For example, a user can create a scheduled policy to enforce internet usage restrictions during business hours in a specific timezone.

Use Case Examples

  1. Create a scheduled policy named 'Work Hours' for an organization with ID 123, specifying policy IDs for time blocks and setting the timezone to 'America/New_York'.
  2. Automate the creation of multiple scheduled policies with different names and timezones to manage network access schedules across various departments.

Properties

Name Meaning
Additional Fields Optional fields to specify details of the scheduled policy such as name, organization ID, policy IDs representing time blocks, and timezone for localization.
Options Additional request options including custom request body, headers, query filters, batching settings, debug mode, pagination settings, and request timeout.

Output

JSON

  • json - The JSON response from the DNSFilter API representing the created scheduled policy or error information.

Dependencies

  • DNSFilter API key credential for authentication

Troubleshooting

  • Ensure the API key credential is correctly configured and has the necessary permissions to create scheduled policies.
  • Check the format of the 'Policy Ids' JSON array to ensure it matches the expected structure (672 IDs for 15-minute blocks).
  • If rate limiting errors occur, adjust batching settings to reduce request frequency.
  • Enable debug mode to view detailed request and response information for troubleshooting API call issues.

Links

Discussion