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 user agent cleanup task. It is designed to facilitate bulk deletion of user agents that have been inactive for a specified number of days within given organizations. This operation is useful for administrators who want to automate the cleanup of inactive user agents across multiple organizations, helping maintain an up-to-date and efficient user agent database.

Use Case Examples

  1. An IT administrator wants to remove all user agents that have been inactive for more than 30 days across several organizations to free up resources and maintain system hygiene.
  2. A managed service provider (MSP) needs to schedule regular cleanups of user agents that are no longer active in their client organizations to ensure accurate reporting and licensing.

Properties

Name Meaning
Organization Ids List of Organization IDs to target for the cleanup task.
Inactive For The number of inactive days to determine which user agents should be cleaned up.
Additional Fields Optional additional parameters for the cleanup task, including a deprecated single Organization ID.

Output

JSON

  • id - The ID of the created user agent cleanup task.
  • status - The status of the cleanup task.
  • created_at - Timestamp when the cleanup task was created.
  • updated_at - Timestamp when the cleanup task was last updated.

Dependencies

  • DNSFilter API key credential

Troubleshooting

  • Ensure the API key credential is correctly configured and has the necessary permissions to create user agent cleanups.
  • Verify that the Organization IDs provided are valid and accessible by the authenticated user.
  • Check for rate limiting errors (HTTP 429) and implement retry logic or adjust request frequency accordingly.
  • If the node throws errors, enable the debug option to inspect the actual request and response details for troubleshooting.

Links

Discussion