“The telco’s strategy encompasses three broad categories of APIs, each of which targets a different audience:
– Private, internal APIs accessible exclusively to Telstra’s developers;
– External, public APIs, that are available for use by third-party developers; and
– APIs intended for use by Telstra’s partners.
“Each one of these has a different value to Telstra,” said Telstra developer evangelist Frank Arrigo. “The internal ones, the private ones, it’s all about, over time, saving money through driving reuse and reducing duplication and redundancy.”
“The public ones, it’s all about helping drive innovation with our customers,” he said. “Really the value [to Telstra] there is to put services out there that help others create value for themselves. We see ourselves as part of that value chain, helping the developers who are creating a service and an application around it.”
The third category of APIs help Telstra strengthen its relationship with its partners as well as open up new revenue opportunities, he said.”
Article on Computerworld.
The small-grid model discussed here previously, relies on APIs in the same way cities rely on their roads, sewers, electricity grids, etc.
APIs as a revenue stream and business flexibility enabler are in their relative infancy but examples such as the one at Telstra above show that effort is being applied to make them more sophisticated for use by more modular OSS and beyond.Read the Passionate About OSS Blog for more or Subscribe to the Passionate About OSS Blog by Email