A set of APIs that expose network capabilities over HTTP. OneAPI is developed in public and based on existing Web standards and principles. Any network operator or service provider is able to implement OneAPI.
OneAPI version 2.0 specifications
OneAPI v2 includes all of the v1 APIs (SMS, MMS, Location and Payments) as well as Voice Call Control, Data Connection Profile and Device Capability. OneAPI v2 is RESTful, the OneAPI v1 APIs are also available in a SOAP binding - please see the Access API Wiki for the specifications.
Sandbox server
Please visit our GIT repository for a free, open source (LGPL) OneAPI server in PHP/Java.
How does OneAPI work with other mobile and Web APIs?
The GSMA OneAPI is intended to complement existing client-side and Web APIs by providing a missing piece: access to network capabilities and information, regardless of operator, and via Web applications rather than simply device clients.
Canadian Pilot of OneAPI now live!
We are proud to announce the first commercial pilot of OneAPI, with the three Canadian network operators Bell, Rogers and Telus implementing gateway provided by AePona. Developers can sign up once to access location, payments and messaging across all the operators via the OneAPI gateway. For this pilot the gateway has been provided by AePona, and includes payment settlement and privacy management, together with GSMA Pathfinder number portability lookup. You can register, help collaborate and develop at:
What's next?
In our next release OneAPI v2.0 we aim to include 'Data Connection Profile' (lookup the network name and bearer); Click-to-call from a Web page; Web-controlled conferencing; Video Quality (request a Quality of Service to ensure video streams are jitter free and establish that they have been delivered) plus Triggering ('wake up' a device application with SMS/UDH and other technologies). Plus other popular suggestions!
How can I get involved?
¢Benefits for developers and publishers:
-
–add network capabilities to your development toolkit
-
–Reduce proprietary integrations to multiple operators
-
mashup network APIs into desktop and mobile Web applications
¢
Benefits for Mobile operators
-
–Lower the barrier to entry for Web providers by offering a standard entry point to your network
-
–Encourage innovative 3rd parties to deliver services to your customers
-
help avoid fragmentation of network APIs
¢Benefits for aggregators
-
–Facilitate integration into participating operators
-
Offer a consistent set of functionality across operators
-
Attract new developers via a Web-friendly industry standard
¢Benefits for the consumer
The GSMA OneAPI has been based on profiling existing industry standards where possible in order to avoid ‘reinventing the wheel’.
By utilising this site, you will be able to collaborate on the evolution of the API, feedback on the API’s proposed and on their implementation, follow the progress of the project, download documentation and test materials (when available) and help ensure that the API meets the goal of facilitating mobile Web application deployment.
To navigate this site - please use the Link bar just below the GSMA logo at the top of the page.