The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This preface describes the audience, organization, and conventions of the Cisco MSE API Guide, Release 8.0 and contains the following sections:
This document is intended for developers who wish to implement the MSE RESTFul client support on the Mobility Services Engine application. The audience is assumed to be familiar with RESTful Web services and the HTTP protocol.
This guide uses the following conventions:
Tip Means the following information will help you solve a problem.
The Reports REST API embraces several aspects of the HTTPS standards, including some headers, HTTP verbs, and status codes. The REST API uses status codes that are only supported in the HTTP/1.1 version. Therefore, it is expected that the client consuming this API complies with these HTTP/1.1 features.
This REST API is used for reading location data and providing notification when specific conditions are met. It supports the HTTPS GET, PUT, and DELETE methods.
Follow these steps to obtain documentation updates and related documentation for the context-aware API:
For any additional questions on usage of the APIs or details of the information that can be retrieved from MSE. The Cisco MSE Developer Community Web portal is located at Mobility Services API Developer Center.