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 operation checks the status of a bulk update job for networks in the DNSFilter API. It is useful for monitoring the progress or result of a bulk update operation on multiple networks, such as when updating network configurations or policies in batch. For example, after initiating a bulk update of network settings, this operation can be used to poll the status of that update job to determine if it has completed successfully or if there were any errors.

Use Case Examples

  1. Check the status of a bulk update job by providing the job ID to monitor its progress.
  2. Use it in workflows that automate network management to handle bulk updates efficiently and track their completion.

Properties

Name Meaning
Id The ID of the bulk update job to check status on.
Options Additional optional settings such as custom request body, headers, query filters, batching, debug mode, pagination, and timeout.

Output

JSON

  • id - The ID of the bulk update job.
  • status - The current status of the bulk update job.
  • progress - Progress details of the bulk update job, such as percentage completed.
  • errors - Any errors encountered during the bulk update process.

Dependencies

  • An API key credential for DNSFilter to authenticate requests.

Troubleshooting

  • Ensure the provided bulk update job ID is correct and exists.
  • Check API key credentials and permissions for accessing bulk update status.
  • If rate limited, use batching options to reduce request frequency.
  • Enable debug mode to see detailed request and response information for troubleshooting.

Links

Discussion