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 identified by its UUID. It is useful for scenarios where you need to fetch and analyze data about a particular user agent within your network or organization, such as monitoring agent status, version, or other attributes.

Use Case Examples

  1. Fetch detailed information about a user agent by providing its UUID to monitor its status or configuration.
  2. Retrieve user agent details for troubleshooting or auditing purposes.

Properties

Name Meaning
Id The UUID of the user agent to retrieve information for. This is a required string parameter.
Options Additional optional settings for the request, including custom body, headers, query filters, batching, debug mode, pagination, and timeout settings.

Output

JSON

  • id - The UUID of the user agent.
  • type - The type of the user agent.
  • attributes
    • hostname - The hostname of the user agent.
    • friendly_name - The friendly name of the user agent.
    • agent_version - The version of the user agent software.
    • status - The current status of the user agent.
    • state - The current state of the user agent.
    • last_sync - The last synchronization time of the user agent.
    • network_id - The ID of the network the user agent belongs to.
    • organization_id - The ID of the organization the user agent belongs to.

Dependencies

  • An API key credential for DNSFilter API authentication.

Troubleshooting

  • Ensure the provided user agent UUID is correct and exists in the DNSFilter system.
  • Check that the API key credential is valid and has the necessary permissions to access user agent information.
  • If the node returns rate limit errors, consider using the batching options to limit request frequency.
  • Enable debug mode to get detailed request and response information for troubleshooting.

Links

Discussion