An Introduction to APIs

What it is? Why use it?

1. An Introduction to APIs
What is it? Why use them?

2. What is an API?

3. Why mobile backends do not respond with HTML?
3
It is hard for
the app to
understand
HTML

4. What is an API?
●When a site is intended for machines (e.g., agents,
apps, systems that act on behalf of humans), we call it
an API
●It is an API
⦿When Delivered over the network
⦿Intended for machines
⦿Used by somebody other than it’s authors

4

5. From Internet of Sites to Internet of APIs
5

6. Why APIs? For individual
●Let us have a richer experience (e.g., browser vs. mobile app)
●Let us automate easier.
⦿Having personal agents (e.g., Siri, find me the best deal for a
camera)
⦿Personal Stocks triggers

6

7. Why API? Organizations
●Each organization is a system of systems
⦿E.g., Payroll, CRM, HR software, etc
●It enables reuse
⦿Systems we build can use data and functionality of others.
⦾e.g., do not write your email sender, use Twilio
⦾e.g., get currency through an API instead of using EOD value
●It enables may systems to work as a single system.
⦿Integrate data and services across different systems and vendors
(e.g., booking multi-hop journey)
⦿Increase automation
●Unleash creativity by let others build on top of your APIs

7

8. API Economy/ API Marketplace
●Just like the internet of sites need search engines, the internet of
APIs need a marketplace to find APIs
●When it comes to APIs, we are still in the early days of internet
where you heard about a web page from friends and went there

8

9. Why Organizations Participate in API Economy
●Pros
⦿Shorter time to market
⦿To make money through core competencies
⦿Save money through reuse
⦿Get better services for a lower cost
⦿To have a small footprint and less complexity
⦿Cheaper in the long term
●Cons
⦿Latency could be a challenge
⦿Increase external dependencies
⦿Could be expensive in the shotterm

9

10. APIs as alternative Delivery Model / Business Models
●Common Advantages for both “software as API” and Data as API
⦿Easy to update/ deliver
⦿Easier to manage old versions
⦿Better Governance - Easy to cancel/ control
⦾e.g., OpenAI exposing models via API to make sure they can govern
⦿Pay for use
●Deliver data as APIs
⦿not give all data at once, only what is needed - not giving a way to dump all data

10

11. How does it work?
●From the user point of view
⦿Find APIs
⦿Subscribe and get keys/ secrets
⦿Test by talking to sandbox URLs
⦿Integrate to the real system
●From the provider point of view
⦿Write n Service / Existing Service
⦿Publish the API to a market place
⦿Intercept API calls, check for security, throttle, enforce subscription, etc.
⦿Provide HA/ Scale

11