Q: What are Enablers?

A: A: "Enabler" is our jargon free name for an API, which stands for Application Programming Interface. In simple terms these Enablers provide access to features of the O2 UK network and infrastructure in a secure and managed way. Please ensure you review and understand sections 5.11, 7.1 and 13.2 of the O2 Litmus Developer Terms and Conditions before using this functionality.

Q: Which Enablers are available?

A brief description of the Enablers and their functionality is provided below. For detailed Developer guides covering each Enabler, please visit the Tools section of O2 Litmus, which is accessible once you are signed in with a Developer account.

Location Enabler: The Location Enabler accepts the O2 Litmus Members mobile phone number, which it passes to the core O2 UK mobile network to obtain and return the coordinates of the handset. The location of the O2 Litmus member is returned in the following format:"51 27 3.35N|0 7 39.29W|1046" This information can be used to power your location application or used in mash up’s with 3rd party mapping engines.

Network Connection Status Enabler: The Network Connection Status Enabler provides key functions to enable O2 Litmus Developers to query the O2 UK Cellular Network Bearer when an O2 UK customer is connected to the Internet through their mobile handset. Via calls to this Enabler, Developers will be able to ascertain if the customer using their application is connected to the O2 UK cellular network on either a GPRS (2.5G) or UMTS (3G) speed connection. This information is important as it allows developers to customise the user experience of their application e.g. deliver low res images or video to 2.5G connections, and high res images and video to 3G connections.

View Device Compatibility Enabler: The View Device Compatibility Enabler can be used to retrieve information about a customer’s device, using an input variable of mobile phone number or brand and model. This information includes screen dimensions, battery life, DRM, the camera type (if available), supported media types, connectivity methods and memory size. Please read the Developer Guide for the full list of features.

Manage Device Enabler: The Manage Device Enabler provides a set of flexible functions which allow a developer to query the range of handsets supported by O2, and also to gain specific information about a particular handsets capabilities. Examples include identifying which manufacturers and models are supported by O2, a URL pointing to a valid device image, and the capabilities of an individual customers device based on a phone number query.

Manage Pay Monthly Bolt On's Enabler: The Manage Postpay Bolt Ons Enabler can be used to retrieve information about select kinds of Bolt Ons that an O2 customer on a pay monthly tariff has subscribed to. If your application is “data heavy”, this Enabler will help to provide a good customer experience to the end user of your application, as you can check if the customer has a mobile data or Wi-Fi Bolt On added to their account. Using the response to this query, you can build logic into your application that then provides context sensitive feedback to the customer.

View Account Status Enabler: The View Account Status Enabler provides the ability to retrieve read only information on the status of an O2 customer’s account, providing details on various products and services that the customer may or may not have enabled on their account. This Enabler will allow the Developer to customise the user experience of their application sign up process and operation to each individual customer. The getBarringCodes operation provides barring codes related to a customer’s phone number. Please read the Developer Guide for the full list of features.

Q: I forgot to tick the appropriate API box when I published my app, or I have changed my mind – can I edit how much app uses the Enablers?

A: Once your app has been published you cannot edit how your app uses the O2 Enablers. This is because behind the scenes O2 Litmus configures permissions to the Enablers using your apps unique app ID number and this process cannot be undone. If you need to change your apps usage of the Enablers you will need to remove your app from O2 Litmus and repeat the "Launch an app" process selecting the correct Enabler configuration.

Q: Where can I find out detailed information on the O2 Litmus Enablers?

A: Please visit the ‘Tools’ section of O2 Litmus which is visible when you are signed into O2 Litmus with a Developer account. Here you will find the Developer Guides to each Enabler on offer.

Q: How much do the Enablers cost to use?

A: Information is available the ‘Tools’ section of O2 Litmus which is visible when you are signed into O2 Litmus with a Developer account. Here you will find the Developer Guides to each Enabler on offer.

Q: Which platform are the O2 Enablers implemented on?

A: The O2 Litmus Enablers are implemented by means of Web Services based on SOAP requests.

Q: Which programming languages can be used to access the Enablers?

A: O2 Litmus has language-independent Enablers that are written in a way that means they can be called from several programming languages. You can find examples of different language implementations in Developer Guides, which can be found in the ‘Tools’ section of the site.

Q: Are there more Enablers coming?

A: We will be working hard to release new Enablers to the O2 Litmus Community as and when appropriate. If there is an Enabler you would like to see be sure to tell us via the Developer Forums. Enabler announcements will be made via the O2 Litmus Blog and Forums.