Lately, I’ve had a lot of people using the Airwave Management Platform (AMP) ask about how to integrate AMP with existing customer portals.

Luckily, the AMP server contains an XML API that allows customers to access all sorts of information that they are used to seeing in the AMP GUI. All of these API’s are documented on the Home -> Documentation page.

One use case for using the XML API is to look up clients by MAC address on the wireless network using a third party application. The API call looks like this:
https://xxx.xxx.xxx.xxx/client_search.xml?query=4b:5c

In this case, we want to know about all users that have ‘4b:5c’ in their MAC address. The output includes (among other items), the full MAC address of the client, username, DNS name of the device, and VLAN id. This data can be used for all sorts of purposes in custom portals and external applications.

Another way to access data is to ‘scrape’ screens directly from the Airwave GUI. For those of you who have AMP installed today, you’ve probably noticed that in the URL, there are a lot of pages that end with ‘?id=xxxx’. An example of this would be the AP Monitoring page. Normally, the URL for that page looks like the following:
https://xxx.xxx.xxx.xxx/ap_monitoring?id=12810.

This URL will get the AP page with all the navigation tools bar and AMP status information at the top of the page. But, what if you just want the AP information to insert into another portal page? By inserting a ‘/nf/’ into the URL, we can access just the AP monitoring data. Using the same URL example above, we end up with this URL:
https://xxx.xxx.xxx.xxx/nf/ap_monitoring?id=12810.

These are only two simple examples, but the reality is that with just a little bit of creativity, you can really unleash the power of AMP in to your custom applications.