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
Infrastructure Service → Create
AI-generatedSummary
Create a new infrastructure service in Infoblox by submitting specified field mappings and optional additional JSON body content with optional additional query parameters.
Inputs
- Fields (required) — Define the fields and their values for the new infrastructure service using a resource mapper that loads the API schema for valid field names.
- JSON Body — Provide additional JSON key-value pairs to extend or override fields not covered by the schema-based mapping.
- Query Parameters — Add extra query parameters as name-value pairs to modify the API request, useful for filters or other API options.
Output shape
a single record representing the created infrastructure service resource, including its properties as returned from the Infoblox API
The output is the API response converted into JSON. The structure depends on the Infoblox API's response for infrastructure service creation.