Actions182
- Address Block Actions
- Audit Log Actions
- Auth Profile: LDAP Actions
- Auth Profile: OIDC Actions
- Auth Profile: SAML Actions
- CDC Application Actions
- CDC Destination: HTTP Actions
- CDC Destination: Splunk Actions
- CDC Destination: Syslog Actions
- CDC Host Actions
- Custom API Request Actions
- DFP Service Actions
- DHCP Fingerprint Actions
- DHCP Lease Actions
- DNS Event Actions
- DNS Record Actions
- DNS Zone Actions
- Endpoint Device Group Actions
- Endpoint Roaming Device Actions
- Endpoint VPN Profile Actions
- Fixed Address Actions
- Global Search Actions
- Identity: Compartment Actions
- Identity: Group Actions
- Identity: User Actions
- Infrastructure Host Actions
- Infrastructure Service Actions
- IP Address Actions
- IP Space Actions
- IPAM Range Actions
- Location Actions
- Lookalike Domain Actions
- Lookalike Target Actions
- NIOS Custom API Request Actions
- NIOS WAPI Object Actions
- NTP Service Config Actions
- Redirect: Custom Redirect Actions
- Service Log Actions
- SOC Insight Actions
- Subnet Actions
- TD Access Code Actions
- TD Application Filter Actions
- TD Category Filter Actions
- TD Internal Domain List Actions
- TD Named List Actions
- TD Scheduled Report Actions
- TIDE Batch Actions
- TIDE Dossier Lookup Actions
- TIDE Threat Actions
TD Category Filter → Update
AI-generatedSummary
Update a Threat Defense category filter in Infoblox by specifying its resource ID and the fields to modify, with optional additional JSON body data and query parameters.
Inputs
- Resource ID (required) — The Infoblox resource ID of the TD Category Filter to update.
- Fields (required) — The fields and their values to update on the TD Category Filter, selectable via a resource mapper supporting schema-based field selection.
- JSON Body — Additional JSON to merge over the mapped fields in the request body, useful for fields not in the schema or custom data.
- Query Parameters — Additional query parameters to append to the API request URL.
Output shape
a single updated TD Category Filter object
The operation returns the updated resource object as JSON. The update is performed via an HTTP PATCH, PUT, or POST request depending on resource-specific method. All supplied fields are merged into the request body.