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 user agent cleanup record in the DNSFilter system. It is useful for managing bulk deletion jobs of user agents, such as starting a cleanup process or modifying the inactivity period that triggers cleanup. For example, an administrator can update a cleanup job to start the cleanup or adjust the number of inactive days before user agents are considered for deletion.

Use Case Examples

  1. Update a user agent cleanup job to start the cleanup process.
  2. Modify the inactivity period for a user agent cleanup job to 30 days.

Properties

Name Meaning
Id The unique identifier of the user agent cleanup to update.
Additional Fields Optional fields to update on the user agent cleanup, including 'Start' to initiate the cleanup and 'Inactive For' to set the number of inactive days.

Output

JSON

  • debug - Debug information including the actual URL, query parameters, headers, and body sent for the API request.
  • * - The JSON response from the API representing the updated user agent cleanup.

Dependencies

  • An API key credential for DNSFilter to authenticate requests.

Troubleshooting

  • Ensure the 'Id' parameter is provided and valid; missing or incorrect IDs will cause errors.
  • If the API rate limit is exceeded, the node will throw a 429 error; consider using batching and intervals to avoid this.
  • Enable the 'Debug' option to get detailed request and response information for troubleshooting.

Links

Discussion