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 updates the policies associated with a specific application within an organization. It allows users to specify which policies should be allowed and which should be blocked for the given application. This is useful for managing application access and security policies in an automated workflow.

Use Case Examples

  1. Updating the allowed and blocked policies for a particular application in an organization to enforce security rules.
  2. Automating policy updates for applications when organizational changes occur, ensuring compliance with security standards.

Properties

Name Meaning
Allow Policies List of Policy IDs to be allowed on a specific application.
Application Id The ID of the application for which policies are being updated.
Block Policies List of Policy IDs to be blocked on a specific application.
Organization Id The ID of the organization that owns the application.
Options Additional optional settings such as custom request body, headers, query filters, batching, debug mode, pagination, and timeout settings.

Output

JSON

  • allow_policies - List of allowed policy IDs for the application.
  • application_id - The application ID for which policies were updated.
  • block_policies - List of blocked policy IDs for the application.
  • organization_id - The organization ID that owns the application.

Dependencies

  • An API key credential for authentication with the DNSFilter API.

Troubleshooting

  • Ensure that the API key credential is correctly configured and has the necessary permissions to update policies.
  • Verify that the application ID and organization ID are valid and exist in the system.
  • Check the format of the allow_policies and block_policies JSON arrays to ensure they contain valid policy IDs.
  • If the node returns rate limit errors (HTTP 429), consider adjusting the batching and batch interval options to reduce request frequency.
  • Enable debug mode to get detailed request and response information for troubleshooting.

Links

Discussion