Introducing SOC Insights for BloxOne Threat Defense: Boost your SOC efficiency with AI-driven insights to eliminate manual work and accelerate investigation and response times. Read the blog announcement here.

Best Practices


Why use Infoblox WAPIs?

With an increase in demand for higher efficiency at lower costs, automation has become very critical for all businesses. Organizations have started to adopt various automation strategies, like using existing tools designed for a specific automation purpose or building tools/scripts on their own.


Catering to these growing demands, Infoblox offers Web-based Application Programming Interfaces, also called WAPIs, which allow you to easily integrate NIOS into your automation environment.


Why use Infoblox WAPIs?


Infoblox WAPI is an interface based on REST (REpresentational State Transfer), also called a RESTful web API. REST is an architectural style that uses simple HTTP calls for inter-machine communication instead of more complex options like CORBA, COM+, RPC, or even SOAP. Using REST means your calls will be message-based and reliant on the HTTP standard to describe these messages.



Using the HTTP protocol means REST is a simple request/response mechanism. Each request returns a subsequent response. You can see a simple example below.


WAPI pic1.png




Requests are made up of a verb (GET, as shown in the above example), headers that describe the message, and a body. The request is a message that describes what you want the server to accomplish. Likewise, the response consists of three pieces: a status code (200), headers describing the response and the body itself.

Infoblox WAPI supports the primary or most-commonly-used HTTP Verbs that describe the type of operation:

  1. GET: Retrieve a resource
  2. POST: Create a resource
  3. PUT: Update a resource
  4. DELETE: Delete a resource

Available Out-of-the-Box

The WAPIs are shipped out-of-the-box with the Infoblox Grid. It does not require a separate server. The documentation for all the WAPIs is also available at “https://<grid-master-IP/wapidoc.”


WAPI pic2.png

Independent of any Language or developer tool

The WAPI calls can be made with any language that the developer is comfortable with, reducing the implementation time. Also, most automation tools available in the market, like HP Operations Orchestrator and ServiceNow, support making REST calls. This makes it easier to integrate with WAPIs into your existing IT automation infrastructure. This also allows you to build the infrastructure for your organization with fewer worries about the longer-term committing to a particular client-side stack.


Many tools and frameworks are available

Lots of applications like POSTMAN and Insomnia are available that make it easy to test, develop and generate code for the WAPI calls. Both the applications are powerful REST API/HTTP clients that allow you to make WAPI calls, club the calls together to save and distribute, amongst other functionalities.


The below image shows a snippet from POSTMAN.


WAPI pic3.png


The Code option gives you a choice to generate a code snippet with the WAPI call in a language of your choice.


WAPI pic4.png


What tasks can be automated using the WAPIs?

All tasks performed from the Grid User Interface can be automated using the Infoblox WAPIs. A few sample calls are listed below.



Create a network


WAPI create.png


Fetch all networks


WAPI Fetch.png


Delete a network


 WAPI Delete.png



Infoblox WAPIs are simple, easy to use and powerful REST-based APIs that allow you to interact with the Infoblox Grid to automate your processes.



Showing results for 
Search instead for 
Did you mean: