API Fundamentals

What Is an API?

An API, or Application Programming Interface, is a set of rules that allows different software applications to communicate with each other. It's not an application you can see, but an invisible layer that makes modern digital life possible.

Think of an API like a waiter in a restaurant. You, the customer (a client application), want something from the kitchen (a server). You don't go into the kitchen yourself. Instead, you give your order to the waiter (the API). The waiter takes your request to the kitchen, gets your food, and brings it back to your table. The API does the same thing, but with data.

The API acts as an intermediary, taking a request from one application, communicating it to another, and then returning a response. This allows developers to use features from other services without needing to know how those services work internally.

How APIs Communicate

API communication relies on a standard request-and-response pattern. The client sends a request to a specific location, and the server sends back a response. This interaction is defined by a few key components.

Endpoint

noun

A specific URL where an API can be accessed. Each endpoint represents a particular function or resource. For example, https://api.example.com/users could be an endpoint to access user data.

When making a request to an endpoint, the client must specify what it wants to do. This is done using HTTP methods, which are essentially verbs for the API.

Method	Action	Example Usage
GET	Retrieve data	Get a specific user's profile
POST	Create new data	Add a new user to the system
PUT	Update existing data	Change a user's email address
DELETE	Remove data	Delete a user's account

After the server processes the request, it sends back a response that includes the data you asked for (if any) and an HTTP status code. This code tells you whether your request was successful, if there was an error, or something else.

You've likely seen a 404 status code when a webpage can't be found. APIs use a wider range of codes to provide specific feedback. A 200 OK means everything worked, while a 401 Unauthorized means you don't have permission to access the resource.

Languages and Styles

APIs need a structured way to format the data they exchange. The two most common formats are JSON and XML.

JSON (JavaScript Object Notation) is lightweight and easy for both humans and machines to read. It uses key-value pairs and is the most popular format for modern APIs.

XML (eXtensible Markup Language) is a bit older and more verbose. It uses tags to define elements, similar to HTML. While less common for new web APIs, it's still used in many enterprise systems.

// JSON Example
{
  "user": {
    "id": 123,
    "name": "Alex",
    "email": "alex@example.com"
  }
}

<!-- XML Example -->
<user>
  <id>123</id>
  <name>Alex</name>
  <email>alex@example.com</email>
</user>

Beyond data formats, APIs are also designed with different architectural styles or protocols. These styles define the rules and constraints for how the API should be built and behave.

REST (Representational State Transfer) is an architectural style, not a strict protocol. It's the most common approach for web APIs. RESTful APIs use standard HTTP methods (GET, POST, etc.) and are stateless, meaning each request is independent and contains all the information needed to be understood by the server.

SOAP (Simple Object Access Protocol) is a more rigid protocol with strict rules. It often relies on XML for its message format and has built-in standards for security and error handling. It's generally seen as more complex and is often used in enterprise environments.

GraphQL is a query language for APIs developed by Facebook. Unlike REST, which has multiple endpoints for different resources, GraphQL typically uses a single endpoint. It empowers the client to ask for exactly the data it needs, which can prevent over-fetching (getting more data than necessary) or under-fetching (having to make multiple API calls to get all required data).

Now that you understand the basic building blocks, let's test your knowledge.

Quiz Questions 1/5

In the common analogy of a restaurant, what role does the API play?

Quiz Questions 2/5

What is the primary purpose of an HTTP status code in an API response?

Understanding these core concepts is the first step toward effectively managing, designing, and strategizing API products.

API Product Management Mastery