XML API DeprecationGetting StartedREST API BasicsComplianceWebhooksWebex APIs
Webex Assistant Skills
Full API Reference
API Changelog

Historical API

Please be aware that the endpoint for these functions is analytics.webexapis.com, which also means that the ‘try-it’ mode won’t work. If you have any questions, or if you need help, please contact the Webex Developer Support team at devsupport@webex.com.

This interface allows an IT Admin to pull analytics data from the data backend without having to interact with the UI or perform any manual steps.

To access the API, the access token must represent an admin with either read-only-admin or full-admin roles for the given org. In addition, the access token must have the analytics:read_all scope

By default, the calls to analytics.webexapis.com for historical data are sent to closest region servers. If the region servers host the organization's data, then the data is returned. Otherwise, a http 451 error code response will be returned. The body of the response in this case contains the end point information from where user can get historical data for the user's organization.

Following is an example of how the error message looks like: { "message": "This server cannot serve the data for this organization. Please use {another region's VIP}", "errorCode": 451, "trackingId": {trackingId} }

To use this API the org needs to be licensed for pro pack.