Aruba’s Instant On product line consists of plug and play access points and switches that are managed from the cloud. The cloud management portal – located at https://portal.arubainstanton.com – is free and does not require purchasing any license.
While it provides an intuitive UI for setting up and managing networks, it is not conducive for automation. For example, if someone is managing many sites and needs to apply policies in bulk to all of them, or monitor their status, it would be very time-consuming and tiresome to do it manually.
Aruba does not provide an API for interacting with their cloud portal. However, an API does exist under the hood and was reverse-engineered in this excellent post. It mentions many of the common API endpoints and provides Powershell scripts for communicating with the API and getting data from it.
Using the Postman Collection
Open the companion Postman collection and download it to your system by clicking on “Run in Postman”.
After opening it in Postman go to environment and add your Aruba cloud’s login credentials in it:
The collection is divided into 2 folders. Authorization folder contains a series of requests that – when run in sequence – result in the final bearer token that is required to be used with requests in the second folder named Requests.
Getting Data from API
It appears that almost everything that can be done from the web portal can be done via API as well. For example, to fetch site list use the sites endpoint:
This provides a count of sites administered by that account and includes various details such as the id of each site. The id will be used subsequently to identify that site when making site-specific requests.
The clientSummary endpoint gives details of clients currently connected to the network:
Similarly, there is an inventory endpoint for getting details of the Aruba Instant On hardware on site:
The companion Postman collection includes more endpoints such as alerts, administration, and guestPortalSettings.
Making Changes via API
Some API endpoints can be used for making changes by issuing requests using HTTP PUT verb. Suppose we want to change the RADIUS server being used for authorizing guests on the network. We will first fetch the existing settings using guestPortalSettings endpoint:
We will copy the complete JSON returned in response body, and substitute the new RADIUS address and secret in serverHost and sharedSecret parameters. Then we will issue a PUT request to the same API endpoint: