API(APPLICATION PROGRAMMING INTERFACE)
Application Programming Interfaces
An Application Programming Interface (API) is a contract that allows code to talk to other
code. APIs are the building blocks of modern software because they allow for sharing of
resources and services across applications, organizations, and devices.
Have you ever made a payment on a website? Checked the weather on a mobile app?
Listened to Spotify on both your desktop and your phone? Used Google Maps inside another
app? Whether you know it or not, you are using APIs every day. Even this lesson you are
reading is brought to you by an API!
Why are APIs important?
1. APIs help developers integrate exciting features and build automation without
reinventing the wheel
ex: using a Weather API instead of launching your weather balloons
2. APIs allow enterprises to open up their product for faster innovation
ex: apps that interact with Twitter or Meta APIs by posting on your behalf or reading
tweets
3. APIs can be products themselves
ex: Software as a Service (SaaS) products like Stripe's payment APIs or Twilio's text
messaging and email APIs
Who works with APIs?
APIs are not just for developers. According to Postman's latest State of the API Report,
almost half of the survey respondents identified as holding non-developer roles, such as
management, solutions architects, business and data analysts, educators and researchers.
All these roles benefit from the standardized data access provided by APIs.
API use is not limited to the tech and IT industries. Survey responses in the same report
show that while tech, business, IT, and banking sectors represent the bulk of API use, any
industry can benefit from the convenience provided by API
Who benefits from APIs? Ultimately, everyone benefits from APIs either directly or
indirectly because APIs make processes more efficient and connect the services we love and
rely on
APIs - A Digital Restaurant You can think of APIs as being like a waiter at a restaurant,
serving as a go-between for the customer and the kitchen
A customer who wants soup doesn't go into the kitchen to cook. They don't even have to
know how to make soup! They only have to know how to ask the waiter for soup, expecting
the waiter to bring back soup.
APIs work the same way, but there are different names for the players involved. Instead of
soup, the requester might ask for data or execution of a service.
Networking term Description Restaurant analogy
Client The requester. Ex: browser, web app, mobile app Customer
Simplified interface for interacting with the
API Waiter
backend
Server The backend where the processing happens Kitchen