Skip to main content
GSMA Logo

3rd Party Access Project - OneAPI

Go Search
Home
Access API Wiki
LIVE Canada Pilot
LIVE Reference Implementation
FAQ
Contribute to the project
  

What is OneAPI?
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 1.0 candidate release specifications
 
OneAPI is available as RESTful and SOAP definitions for SMS, MMS, Location and Payments.
 
For the RESTful version see the Access API Wiki , or this .zip bundle of PDFs (~235 KB). 
For SOAP WSDLs, XML schemas and Apache Axis scripts, please see this .zip bundle (75 KB).
 
How does it 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?
Feedback and suggestions are very welcome, please contact the OneAPI team at oneapi@gsm.org . Alternatively please see the forum at the Reference Implementation. We also have a live commercial pilot at http://canada.oneapi.gsmworld.com with more countries to follow.
 
¢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

  • Faster availability of innovative new services

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.
 
 
 
 

 Follow OneAPI on twitter

Follow OneAPI on twitter

 Events Calendar

There are currently no upcoming events.

 Access News and Updates

OneAPI v1 WSDLs now available 
by Kevin Smith
 28/06/2010 12:37
We have just posted the .zip bundle of SOAP WSDLs, XML Schemas and Apache Axis scripts for SMS, MMS , Location and Payments - see www.gsmworld.com/oneapi .
 
OneAPI version 1.0 candidate release specifications now available 
by Kevin Smith
 08/06/2010 15:03
Please see the Access API Wiki for details. The version 1.0 APIs allow you to:
  • send and receive an SMS
  • send and receive an MMS
  • get the location of one or more network users
  • charge a user for services

Both RESTful/JSON and SOAP flavours are supported.

 
OneAPI Hack-a-thon WIPJam roadshow! 
by Kevin Smith
 04/05/2010 13:37
WIPJam will be hosting their excellent developer jams in Montreal, Toronto, Ottawa and Vancouver throughout May: see http://www.wipconnector.com/wipjam/oneapi for full details. Expect a flurry of coding, learn about OneAPI (and give us feedback!), meet...
 
Canadian OneAPI pilot now launched 
by Kevin Smith
 17/02/2010 14:53
Visit http://canada.oneapi.gsmworld.com/ for OneAPI access to Bell, Rogers and Telus. Great to see our first live commercial implementation!
 
OneAPI v1.0 near completion 
by Kevin Smith
 13/01/2010 16:27
The underlying specifications for OneAPI, produced by the OMA, are now in their final tidy-up phase. You can preview there at http://member.openmobilealliance.org/ftp/public_documents/arch/ARC-REST/2010/
 
Note that the OneAPI documentation will be...
 
(More Announcements...)