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 information about a specific User Agent CSV Export by its ID. It is useful for scenarios where users need to track or review the status and details of CSV exports related to user agents within their DNSFilter environment. For example, a user might want to fetch the export status or metadata of a previously initiated CSV export to monitor its progress or download the results.

Use Case Examples

  1. Retrieve details of a User Agent CSV Export by providing its unique ID to monitor export status or metadata.
  2. Use this node to fetch information about a specific CSV export for auditing or reporting purposes.

Properties

Name Meaning
Id Id of user agent csv export, used to specify which export record to retrieve.
Options Additional optional parameters such as custom request body, headers, query filters, batching, debug mode, pagination settings, and timeout to customize the API request.

Output

JSON

  • id - The unique identifier of the user agent CSV export.
  • status - The current status of the CSV export process.
  • createdAt - Timestamp when the CSV export was created.
  • updatedAt - Timestamp when the CSV export was last updated.
  • fileUrl - URL to download the exported CSV file, if available.

Dependencies

  • DNSFilter API key credential

Troubleshooting

  • Ensure the provided Id is valid and exists in the DNSFilter system to avoid 'not found' errors.
  • Check API key credentials and permissions if authentication errors occur.
  • If the node returns empty or incomplete data, verify that the export process has completed successfully before fetching details.
  • Enable debug mode in options to get detailed request and response information for troubleshooting.

Links

Discussion