Channels ▼


An API To Telco-Enhance Your App

Apigee API Exchange arrives this month as an API exchange platform designed to enable the sharing of data and services through apps.

More Insights

White Papers

More >>


More >>


More >>

Initially targeted and made available for the telecommunications industry, this model for API interoperability is hoped to create expanded reach for both operators and developers with "telco-enhanced" mobile app experiences.

Apigee CEO Chet Kapoor says that being able to share services and data through interoperable APIs is crucial to establishing digital ecosystems in any industry.

"This is especially true in industries where competition or regulation has created fragmentation, such as in telecommunications, healthcare, and travel. The API Exchange will let consumers use apps and APIs seamlessly across disparate businesses within an industry, similar to roaming on mobile phones," he said.

"The API Exchange is designed to deliver API federation and simplify the development of apps across any industry where fragmentation is an issue. It provides a flexible solution that allows API providers to use industry standard APIs or their own customized APIs and still interoperate. In an API Exchange-powered ecosystem, application developers can build apps with data that can be consumed by a broad range of users across disparate API providers," he added.

Through the API Exchange, operators expose network APIs such as payment, identity, and messaging, which are federated to provide the cross-operator reach. Developers of apps and web services can integrate these APIs to enrich the functionality and improve the user experience of their apps.

The API Exchange includes APIs for onboarding app and API providers, validation and federation of app usage, metadata management, logging and rating of app usage, and cross-provider billing for financial settlement between providers.

An API To Telco-Enhance Your App

Related Reading

Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dr. Dobb's encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dr. Dobb's moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing or spam. Dr. Dobb's further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.