This is a work in progress. Please let me know what you think about this presentation via twitter or simply high5 me on haikudeck ( @aka20p )

My name is Liad Bokovsky. At the time of writing these notes I am working for Mashery, an Intel Company, and am based in the UK.
Find me on twitter, linkedin, or Yumchaa tea house

* Been around for many years
* Technical Integration Point
* Application Interface between machines and systems

* migration, development, interoperability, technology advancements

* Evolved significantly in the past few years with the growth of services and systems that relay on data exchange

In the beginning, API was a technical integration point. An applications way to communicate between themselves.

* well defined set of commands
* provider and consumer know each other very well
* Machine to Machine

There is a massive increase in API's adaptation and availability since the introduction of the iPhone.

* The smart phone and mobile application really gave API's a boost.
* There is a need for accessible data.
* Quick to access and easy to process

* Developers started dictating the state of the economy.

* Transitioning from a world of Web sites / services to the world of Apps.

* The meaning of this transition

Most API's are internal
Consider opening the API
Drive innovation and attract new users

Companies focus on their business and fail to see what other benefits can their data provide if combined or overlaid on top of other data sets and technologies.

Companies that were early to adopt API's had seen significant growth and were able to adapt and innovate much quicker compared with other companies.

Ancillary Services: Expose key related booking functions to partners

End-to-end Experience: Mashup broad range of functions for inclusivity

Lower On-boarding Costs: Reach tier 2 partners economically

Contextual Targeting: Develop timely offers via mobile

Development and Security: Offload security and performance

Data Service Business: Uncover usage trends and package for GTM

Loyalty Programs: Flexible use of awards across affiliate partners

Create a brand new in-store experience.

Understanding the consumer habits and needs.

Improve customer service.

Signage and APIs.

Building a community means increased number of users,

partnerships and "free" advertising through API licensing.

Developer Communities are becoming the R&D teams driving innovation and exploring new ideas

Consider exposing your API's in a controlled manner through hack days and hackathons

A forum, a portal, documented, support online, events, sample code and a place for developers to share their work

Once an API connection is made, it forms a relationship between the API vendor and the developer.
A trust.

Don't break it. Don't start upgrading the code or release v2 without a proper migration plan.

Be mindful of the developers needs.

A developer puts a lot of effort into understanding your API. Reading the documentation, defining requirements, programming apps. Don't abuse it.

The developers that learn and use your API put a lot of effort into understanding it, developing with it and turning you into a partner.

like with everything, once you put so much effort into something, moving away from it is not trivial. It creates positive stickiness. a partnership.

Generate more money through affiliation , partnerships, pay-as-you-go and contract of API's.

Very common practice is to enable a simple public API and add more functionality to the paid versions.

So many amazing opportunities out there.
If you open any app on your mobile phone, it is likely using at least one 3rd party API. Let's have a look.

Don't be a stranger.