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 CSV export record. It allows users to specify various filters and options to customize the export, such as filtering by network IDs, user agent type, search keywords, tags, status, state, agent state, and traffic activity. The node is useful for automating the export of user agent data in CSV format for reporting or analysis purposes.

Use Case Examples

  1. A network administrator wants to export a CSV file of all proxy user agents that have been active in the last 15 minutes across specific networks.
  2. A security analyst needs to generate a CSV export of user agents filtered by tags and status to review their activity and compliance.

Properties

Name Meaning
Additional Fields Optional filters and attributes for the user agent CSV export, including user agent export attributes, network IDs, type, search keywords, tags, status, state, agent state, and traffic activity in the last 15 minutes.
Options Additional request options such as custom body JSON, custom HTTP headers, query filters, batching settings, debug mode, pagination settings, and request timeout.

Output

JSON

  • id - ID of the created user agent CSV export record
  • status - Status of the CSV export process
  • created_at - Timestamp when the CSV export was created
  • updated_at - Timestamp when the CSV export was last updated
  • user_agent_csv_export - Attributes of the user agent CSV export as JSON

Dependencies

  • DNSFilter API key credential

Troubleshooting

  • Ensure the DNSFilter API key credential is correctly configured and has the necessary permissions to create user agent CSV exports.
  • Check that the input parameters for filters and additional fields are correctly formatted, especially JSON fields.
  • If the API rate limit is exceeded, the node may throw a 429 error; use batching and interval options to mitigate this.
  • Enable debug mode to get detailed request and response information for troubleshooting API call issues.

Links

Discussion