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 updates a scheduled policy in the DNSFilter system. It is useful for modifying existing scheduled policies by specifying the policy ID and the fields to update, such as name, organization ID, policy IDs, and timezone. This operation is typically used in scenarios where scheduled policies need to be adjusted or corrected without creating a new policy from scratch.

Use Case Examples

  1. Update the name and timezone of a scheduled policy by providing its ID and the new values.
  2. Modify the policy IDs associated with a scheduled policy to change its schedule blocks.

Properties

Name Meaning
Id The unique identifier of the scheduled policy to update, required to specify which policy to modify.
Additional Fields Optional fields to update on the scheduled policy, including name, organization ID, policy IDs (representing 15-minute blocks), and timezone for localization.

Output

JSON

  • json - The JSON response from the DNSFilter API after updating the scheduled policy, containing the updated policy details.

Dependencies

  • An API key credential for DNSFilter API authentication.

Troubleshooting

  • Ensure the provided scheduled policy ID exists and is correct to avoid 'not found' errors.
  • Verify that the API key credential is valid and has permissions to update scheduled policies.
  • Check the format of the policy IDs JSON array to ensure it matches the expected structure.
  • If rate limiting occurs, respect the Retry-After header and retry after the specified time.

Links

Discussion