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 detailed information about a specific user agent bulk update by its ID. It is useful for scenarios where you need to fetch the status or details of bulk updates applied to user agents in your network, such as monitoring update progress or auditing changes.

Use Case Examples

  1. Fetch details of a user agent bulk update by providing its unique ID to monitor the update status.
  2. Retrieve information about a specific bulk update operation to verify changes applied to multiple user agents.

Properties

Name Meaning
Id The unique identifier of the user agent bulk update to retrieve.
Options Additional optional settings such as custom request body, headers, query filters, batching, debug mode, pagination, and timeout to customize the API request.

Output

JSON

  • id - The ID of the user agent bulk update.
  • status - The current status of the bulk update.
  • createdAt - Timestamp when the bulk update was created.
  • updatedAt - Timestamp when the bulk update was last updated.
  • details - Additional details or metadata about the bulk update.

Dependencies

  • An API key credential for DNSFilter API authentication.

Troubleshooting

  • Ensure the provided ID is valid and exists; otherwise, the API will return an error.
  • Check API key credentials and permissions to access user agent bulk updates.
  • If rate limited, adjust batching settings or wait before retrying.
  • Enable debug mode to see the full request and response details for troubleshooting.

Links

Discussion