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 an existing BlockPage resource in the DNSFilter API. It is useful for modifying details of a block page such as its name, organization ID, contact email, logo UUID, and timestamps. This operation is typically used when you need to change the configuration or metadata of a block page that controls how blocked content is presented to users.

Use Case Examples

  1. Update the name and contact email of a specific block page by providing its ID and the new values.
  2. Modify the organization ID and logo UUID of a block page to reflect changes in ownership or branding.

Properties

Name Meaning
Id The unique identifier of the BlockPage to update, required to specify which block page to modify.
Additional Fields Optional fields to update on the BlockPage, including name, organization ID, block organization name, block email address, block logo UUID, created at date, and updated at date.

Output

JSON

  • id - The unique identifier of the updated BlockPage.
  • name - The name of the updated BlockPage.
  • organization_id - The organization ID that owns the updated BlockPage.
  • block_org_name - The name of the organization shown on the updated block page.
  • block_email_addr - The contact email address shown on the updated block page.
  • block_logo_uuid - The UUID of the custom logo on the updated block page.
  • created_at - The creation date of the updated block page.
  • updated_at - The last updated date of the block page.

Dependencies

  • An API key credential for DNSFilter to authenticate requests.

Troubleshooting

  • Ensure the BlockPage ID provided is valid and exists in the DNSFilter system.
  • Verify that the API key credential is correctly configured and has permissions to update block pages.
  • Check for network issues or API rate limits that might cause request failures.
  • If the node returns an error, review the debug output (if enabled) to see the actual request and response details for troubleshooting.

Links

Discussion