AvantGuard - DNSFilter icon

AvantGuard - DNSFilter

AvantGuard - DNSFilter

Actions277

Overview

This node interacts with the AvantGuard DNSFilter API to retrieve information about networks. Specifically, the "Networks All" operation fetches a list of networks with optional filtering and pagination. This is useful for scenarios where you need to manage or analyze multiple network configurations, such as auditing network settings, monitoring network usage, or integrating network data into other workflows.

Practical examples include:

  • Retrieving all networks to display in a dashboard.
  • Filtering networks to get only basic info or exclude IP addresses for privacy reasons.
  • Paginating through large sets of network data to process them in batches.

Properties

Name Meaning
Additional Query Parameters Optional parameters to customize the query:
- Basic Info: Return only the most basic network information (boolean, default true).
- Force Truncate Ips: Exclude IP addresses from the returned network info (boolean, default true).
- Page: JSON object specifying page number and size for paginated results.

Output

The node outputs JSON data containing the list of networks retrieved from the API. The structure typically includes network details such as network IDs, names, and other metadata depending on the query parameters used. If binary data were involved, it would be summarized here, but this node deals solely with JSON network data.

Dependencies

  • Requires an API key credential for authenticating with the AvantGuard DNSFilter API.
  • The base URL for API requests is https://api.dnsfilter.com.
  • No additional external dependencies are indicated beyond the API access.

Troubleshooting

  • Common Issues:

    • Authentication failures due to missing or invalid API keys.
    • Incorrectly formatted JSON in the "Page" parameter causing request errors.
    • Using incompatible combinations of query parameters that might result in empty or partial data.
  • Error Messages:

    • Unauthorized or 401 errors indicate issues with API credentials; verify the API key configuration.
    • 400 Bad Request errors may arise from malformed query parameters; ensure JSON syntax is correct.
    • Network timeouts or connectivity issues suggest checking internet connection or API service status.

Links and References

Discussion