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
AgentLocalUsers → Update
AI-generatedOverview
This node updates an existing agent local user in the DNSFilter system. It is useful for scenarios where you need to modify details of a specific agent local user, such as changing user attributes or settings. For example, updating the user's name, permissions, or other related data by specifying the user ID and the new data in JSON format.
Use Case Examples
- Update an agent local user's details by providing the user ID and a JSON object with the updated fields.
- Modify the permissions or attributes of an agent local user by sending a PATCH request with the new data.
Properties
| Name | Meaning |
|---|---|
| Id | The unique identifier of the agent local user to update. |
| Agent Local User | JSON object containing the update parameters for the agent local user. |
| Options | Additional optional settings such as custom request body, headers, query filters, batching, debug mode, pagination, and timeout. |
Output
JSON
json- The JSON response from the API after updating the agent local user.
Dependencies
- An API key credential for DNSFilter to authenticate requests.
Troubleshooting
- Ensure the 'Id' property is correctly set to the agent local user ID you want to update.
- Verify the JSON structure of the 'Agent Local User' property is valid and matches the API requirements.
- Check API key credentials and permissions to ensure the update operation is authorized.
- If using batching, ensure batch size and interval are configured to avoid rate limiting.
- Enable debug mode to see the actual request and response details for troubleshooting.
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.