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 subnet associated with a network. It is useful for network administrators or IT professionals who need to fetch subnet details for monitoring, auditing, or configuration purposes. For example, you can use this node to get subnet information by providing the network ID and subnet ID, which helps in managing network infrastructure efficiently.

Use Case Examples

  1. Retrieve details of a subnet by specifying the network ID and subnet ID to monitor network segments.
  2. Fetch subnet information for auditing network configurations.

Properties

Name Meaning
Id The ID of the network to which the subnet belongs.
Subnet Id The ID of the subnet to retrieve information for.
Options Additional optional parameters such as custom request body, headers, query filters, batching, debug mode, pagination settings, and timeout.

Output

JSON

  • id - Subnet ID
  • network_id - Network ID the subnet belongs to
  • name - Name of the subnet
  • cidr - CIDR notation of the subnet
  • gateway - Gateway IP address of the subnet
  • created_at - Creation timestamp of the subnet
  • updated_at - Last update timestamp of the subnet
  • additional_properties - Any additional properties returned by the API for the subnet

Dependencies

  • An API key credential for DNSFilter API authentication

Troubleshooting

  • Ensure the Network ID and Subnet ID are correct and exist in the DNSFilter system.
  • Check API key validity and permissions for accessing network subnet information.
  • Enable debug mode to see the actual request URL, headers, and body for troubleshooting.
  • Handle rate limiting by configuring batching and respecting Retry-After headers from the API.

Links

Discussion