Extreme API with Python
Table Of Contents
- 1 Preface
- 2 Introduction
- 3 EXOS APIs
- 4 VOSS API
- 5 XMC API
- 6 ExtremeCloud IQ API
- 7 Extreme Campus Controller API
Extreme API with Python
Page | 119
Part no.9036931-00 Rev AA February 2021
6.1.2 Headers for the xAPI
Because XIQ uses a REST API, connections must be made via HTTPS. Specific headers are required when
making a CALL to the xAPI.
- X-AH-API-CLIENT-SECRET
- X-AH-API-CLIENT-ID
- X-AH-API-CLIENT-REDIRECT-URI
- Authorization
The first three headers are proprietary, and the last one is the regular authorization header.
As the names imply, the first three headers must be configured with, respectively, the Client Secret, the
Client ID, and the Redirect URL generated on the developer portal account. The Authorization header is
a Bearer token, that is, a string containing the word Bearer, with a trailing space, followed with the
Access Token generated in your XIQ account.
6.1.3 xAPI Endpoints
The documentation on the developer portal is the best place to find the correct URL and HTTP methods
supported for each endpoint. All the endpoints are documented with Swagger in the API Details menu.










