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 network by its ID. It is useful for users who need to fetch network details such as network configuration, associated IP addresses count, and other metadata. For example, a network administrator can use this node to get the current state and details of a network within their DNSFilter environment.

Use Case Examples

  1. Retrieve detailed information about a network by specifying its network ID.
  2. Fetch the count of IP addresses associated with a network by enabling the count_network_ips option.

Properties

Name Meaning
Id The unique identifier of the network to retrieve.
Count Network Ips Boolean flag to indicate whether to return the count of IP addresses associated with the network.

Output

JSON

  • id - The unique identifier of the network.
  • name - The name of the network.
  • ip_addresses_count - The count of IP addresses associated with the network, if requested.
  • other_properties - Additional network details returned by the API.

Dependencies

  • DNSFilter API key credential

Troubleshooting

  • Ensure the network ID provided is valid and exists in the DNSFilter system.
  • Check that the API key credential is correctly configured and has the necessary permissions.
  • If the API rate limit is exceeded, wait and retry after the specified Retry-After duration.
  • Enable debug mode to see the full request and response details for troubleshooting.

Links

Discussion