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 retrieve details about a specific user agent cleanup by its ID. It is useful for scenarios where you need to track or audit bulk deletions of user agents within an organization. For example, you can fetch the status and details of a cleanup job to monitor its progress or results.

Use Case Examples

  1. Retrieve details of a user agent cleanup by specifying its ID to monitor bulk deletion progress.
  2. Use the node to fetch information about a specific cleanup job for auditing purposes.

Properties

Name Meaning
Id Id of user agent cleanup to retrieve details for.
Options Additional optional parameters such as custom headers, query filters, batching settings, debug mode, pagination, and timeout settings to customize the API request.

Output

JSON

  • id - Id of the user agent cleanup.
  • status - Status of the user agent cleanup.
  • created_at - Creation timestamp of the cleanup.
  • updated_at - Last update timestamp of the cleanup.
  • details - Additional details about the cleanup process.

Dependencies

  • DNSFilter API key credential

Troubleshooting

  • Ensure the provided Id is valid and exists in the DNSFilter system.
  • Check that the DNSFilter API key credential is correctly configured and has necessary permissions.
  • If rate limited, adjust batching or request intervals to avoid 429 errors.
  • Enable debug mode to see the actual request and response details for troubleshooting.

Links

Discussion