HomeGuidesAPI Reference
GuidesAPI ReferenceGitHubAirheads Developer CommunityLog In

Aruba Central Extensibility

Types of programmable interfaces

Aruba Central offers the following extensibility features which can be leveraged to build custom monitoring, configuration tools, custom dashboards, alerts and notification framework.

  • REST API - For configuration, on-demand polling, monitoring data via HTTP Requests.
  • Streaming API - Subscribe to select topics, get statistics and state changes over Secure WebSocket (WSS).
  • Webhook - Integrate external application and implement actions based on real-time alerts.

REST API

Aruba Central supports a robust set of REST APIs. It allows the users to integrate Aruba Central with their custom applications and tailor the automation needs. By using OAuth 2.0 protocol to authenticate and authorize third-party applications, secure and time-limited access (read/write) to Aruba Central services are provided via REST API.

The REST APIs support standard HTTP methods (GET, POST, PATCH, PUT and DELETE). A HTTP request can be made by providing a specific URL endpoint, HTTP method, access token and data payload. The HTTP response for these requests are returned in the JSON format.

Webhooks

Webhooks allow you to implement event reactions by providing real-time information or notifications to other applications. Aruba Central allows you to create Webhooks and select Webhooks as the notification delivery option for alerts. Using Aruba Central, you can integrate Webhooks with other third-party applications such as ServiceNow, Zapier, IFTTT, and so on. The Webhooks service can be accessed either through the Aruba Central UI or API Gateway.

Streaming API

Aruba Central streaming API follows subscribe-publish model. In this model, a topic is subscribed from Secure WebSocket(WSS) client and Aruba Central will publish continuous data streams to WebSocket client.

This approach is different from client-server model followed by REST API. REST API is conversational in nature where frequent HTTP requests are made by client to obtain latest data. Whereas in streaming API, server sends information to client when available in near real-time.


What’s Next

To learn more about a particular feature go through individual sections linked below.