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...}}}```
Actions256
- Domains Actions
- EnterpriseConnections Actions
- Invoices Actions
- IPAddresses Actions
- MACAddresses Actions
- Metrics Actions
- NetworkLANIPs Actions
- NetworkSubnets Actions
- Networks Actions
- OrganizationUsers Actions
- Organizations Actions
- PoliciesBulkActions Actions
- Policies Actions
- Get extant
- Create
- Get all
- Show policy
- Update
- Delete
- Get application
- Update application
- Add block domain
- Remove block domain
- Add allow domain
- Remove allow domain
- Add block category
- Remove block category
- Add allow category
- Remove allow category
- Add block application
- Remove block application
- Get permissive mode
- Update permissive mode
- PolicyIPs Actions
- PSAIntegrations Actions
- ScheduledPolicies Actions
- ScheduledReportPreviews Actions
- ScheduledReports Actions
- TrafficReports Actions
- Total requests/time
- Total requests/organizations
- Total threats/time
- Total threats organizations
- Total threats clients
- Total threats users
- Total threats collections
- Total category requests
- Category reqs organizations
- Category reqs clients
- Category reqs users
- Category reqs collections
- Total domain reqs
- Domain reqs organizations
- Domain reqs users
- Domain reqs collections
- Total collection reqs
- Collection reqs orgs
- Collection reqs clients
- Collection reqs users
- Queries per second
- QPS organizations
- QPS clients
- QPS users
- QPS collections
- Top domains
- Top categories
- Top application categories
- Top organizations
- Top networks
- Top users
- Top collections
- Query Logs
- Organization stats
- Domain stats
- Category stats
- Total Org Requests
- Total Domain Requests
- Top Organizations Requests
- Total client stats
- Deployments
- Roaming clients
- Application requests
- Application reqs org
- Application reqs clients
- Application reqs users
- Application reqs collections
- Trials Actions
- UserAgentBulkDeletes Actions
- UserAgentBulkUpdates Actions
- UserAgentCleanups Actions
- UserAgentCSVExports Actions
- UserAgentReleases Actions
- UserAgents Actions
- Users Actions
- UserUISettingsV2 Actions
- CybersightCSVExports Actions
- NetworksCSVExports Actions
- AgentLocalUserBulkDeletes Actions
- AgentLocalUsers Actions
- ApiKeys Actions
- ApplicationCategories Actions
- Applications Actions
- Billings Actions
- BlockPages Actions
- Categories Actions
- CollectionUsers Actions
- User(Current) Actions
- DictionaryLookups Actions
- Distributors Actions
- Health Check
- Get
- MSP Search
- Create
- Show MSP
- Update
- Cancel
- Reactivate
- Organizations Search
- Create suborganization
- Show Organization
- Update suborganization
- Cancel suborganization
- Reactivate suborg
- Add Sku
- Remove Sku
- Users Search
- Create user
- Show User
- Add membership
- Update membership
- Remove membership
- Reset password
- Reset password URL
- Get usage info
- Get usage info by SKU
- Get user info by date
- DomainNotes Actions
TrafficReports → Collection reqs orgs
AI-generatedOverview
This node interacts with the DNSFilter API to retrieve traffic report data specifically about the total number of requests by collection for organizations over a specified period. It supports filtering and grouping options to customize the report output, such as filtering by agent IDs, application IDs, date ranges, and more. This node is useful for network administrators or analysts who want to monitor and analyze traffic collections at the organizational level, helping in understanding network usage patterns and security events.
Use Case Examples
- A network administrator wants to get the total number of requests by collection for all organizations in the last 7 days to analyze traffic patterns.
- An analyst needs to filter traffic reports by specific agent types and application IDs to investigate unusual activity within certain collections across organizations.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all results or only a single page. When disabled, no pagination parameters are sent and only one page of results is returned. |
| Additional Fields | Optional filters and parameters to customize the traffic report request, including agent IDs, application IDs, bucket size, date range, MAC addresses, network IDs, organization IDs, private IP ranges, security report flag, grouping options, traffic source, report type, and user IDs. |
Output
JSON
data- The traffic report data returned by the API, containing total requests by collection for organizations.
Dependencies
- An API key credential for DNSFilter to authenticate requests.
Troubleshooting
- Ensure the API key credential is correctly configured and has the necessary permissions to access traffic reports.
- Check that the date and time formats for 'from' and 'to' parameters are correct and in ISO8601 format.
- If pagination is enabled, verify pagination settings to avoid incomplete data retrieval.
- Review the API rate limits and handle 429 status codes by implementing retries or delays as needed.
- Enable debug mode to see the actual request URL, headers, and body for troubleshooting request issues.
Links
- DNSFilter API Tokens - Information on obtaining and using API tokens for authentication.
- DNSFilter API Rate Limits - Details on rate limiting and how to handle it in API requests.