ExtremeLocation Outbound APIs

ExtremeLocation provides a set of APIs to push real-time location data and events for wireless clients that are detected in a venue. These outbound APIs support real-time reporting of events and notifications to an external server (also called a Subscriber). This feature uses either Wi-Fi or Bluetooth Low-Energy (BLE) beacon positioning and is available to all ExtremeLocation customers by default.

Wi-Fi positioning uses existing WLAN infrastructure for location tracking. ExtremeLocation estimates the location of the client device based on the signal strength of 802.11 packets reported by the access points or sensors deployed on the site. With BLE technology, the SDK in the loyalty app on BLE-enabled mobile devices receives the nearest beacon(s) and communicates the beacon IDs to ExtremeLocation to calculate the client location.

These micro-proximity engagement solutions help you identify and locate visitors in the venue, and engage with them by delivering highly customized and contextual messages directly on their mobile devices. You can use the location data and events and integrate them with your CRM and Big Data systems to build custom applications that use real-time location data.

To receive real-time data from ExtremeLocation, you must have a web server in your network capable of receiving and processing the real-time data. You must configure the credentials required for accessing your server through the Subscriber Settings page in the ExtremeLocation GUI. To prevent transmission of data in clear text, Extreme Networks suggests enabling HTTPS support on the your server. Data is presented in JSON format and is encrypted before transmission to your server. For more information, see Setting Up the Remote Web Server.

When an event is generated for any site in the ExtremeLocation account, it is sent to the outbound API handler in real-time. The outbound API handler checks if any filters are to be applied to the event. Filters are used to control the event types to pass to the external web server. The API handler then uses the subscriber connection information to send the filtered events to your web server.

For more information on configuring subscriber settings, see Configuring Subscriber Settings .



This is an unidirectional connection from ExtremeLocation to the subscriber server. The subscriber server cannot send requests to ExtremeLocation.