Infoblox icon

Infoblox

Work with Infoblox Universal DDI, Threat Defense, TIDE, and NIOS WAPI

Actions182

NIOS WAPI Object → Get

AI-generated

Summary

Fetches a single NIOS WAPI object by its _ref via a GET request to the Grid Master and returns it as one output item.

Inputs

  • Object Reference (required) — The WAPI _ref string (e.g. record:host/ZG5zLm...) returned by Infoblox. Each path segment is URL-encoded and used as the endpoint, so it identifies the object directly.
  • Object Type — Shown in the UI (default record:host, or Custom with a Custom Object Type such as record:mx). The Get request uses only the _ref, so this has no effect on the call.
  • Custom Object Type — Free-text object type, shown only when Object Type is Custom. Not used by Get.
  • Query Parameters — Name/value pairs added to the query string, for example WAPI's _return_fields to choose which fields come back. Pairs with an empty name are ignored.

Output shape

One item per input item, containing the WAPI object's JSON (fields depend on the object type and on any requested return fields).

Uses the NIOS credentials (Grid Master URL, WAPI version). The request goes to /wapi/v{version}/{_ref}. If the response isn't a JSON object it is wrapped as {result: value}. With Continue On Fail enabled, errors are returned as {error: message} for that item.

Examples

Example 1: Re-read a host record after finding its _ref in an earlier search

Resource: NIOS WAPI Object; Operation: Get; Object Reference: {{$json._ref}}

Example 2: Fetch a record with extra fields

Object Reference: record:a/ZG5z...:host.example.com/default; Query Parameters: _return_fields = name,ipv4addr,extattrs

Links

Discussion