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 allows users to create a new network in the DNSFilter system by sending a network creation request with specified parameters. It is useful for network administrators or IT professionals who want to programmatically add new networks to their DNSFilter account for monitoring and management. For example, a user can create a network by providing the network details in JSON format, optionally adding custom headers, query filters, batching options, and pagination settings.

Use Case Examples

  1. Create a new network by specifying the network details such as name, IP range, and other attributes in JSON format.
  2. Use batching options to create multiple networks in batches to avoid rate limiting.
  3. Add custom headers or query filters to customize the API request when creating a network.

Properties

Name Meaning
Network Network creation request parameters provided as JSON.
Options Additional optional settings such as custom body JSON to merge with the request, custom HTTP headers, query filters, batching settings, debug mode, pagination configuration, and request timeout.

Output

JSON

  • json - The JSON response from the DNSFilter API after creating the network, including network details or error information.

Dependencies

  • An API key credential for DNSFilter API authentication is required.

Troubleshooting

  • Ensure the API key credential is correctly configured and has the necessary permissions to create networks.
  • Check the network JSON parameters for required fields and correct data types.
  • If rate limiting errors occur, use batching options to limit request frequency.
  • Enable debug mode to see the full request details and troubleshoot issues.
  • Verify the network creation endpoint URL and HTTP method are correct.

Links

Discussion