What Is an API Call?

Think of an API (Application Programming Interface) as a bridge between separate systems; the API call is the actual journey or interaction across that bridge.

The simplest way to describe an API call is that it's a request sent from one system to another in order to get information or perform an action. When you interact with a webpage (for example, selecting something in a dropdown or clicking a button), your browser may send an API call to the company's server to fetch the data it needs. API calls also happen between different companies' servers. For instance, when you buy something online, the store's server often sends an API call to a payment processor (like Stripe or a credit-card company) to authorize and complete the transaction. The other system then sends back a response with the data or the result of the action.

Analogy: An API call is like sending a polite request to a waiter in a restaurant. You don't need to know how the kitchen works — you just tell the waiter what you want (“Bring me a coffee and my friend's profile”), and they bring back exactly what you asked for.

In an app like DuckBuddy — a community for remote workers — every click quietly sends a message such as “Show me people in Europe who enjoy hiking.” The server processes that request and sends back only the useful information: pictures, profiles, chat messages, alerts and recommendations.

Why it matters, even if you're not technical

  • Know why apps feel fast or slow
  • Make better decisions when choosing tools and platforms
  • Feel confident when something breaks (“Is the server down or just this feature?”)
  • Appreciate the magic behind instant chat, smart recommendations and seamless payments

Every API Call Is a Request and a Response

Before the types, the pattern: one side asks, the other answers. That round trip is the whole idea.

Your appThe one that asks — a tap, a search, a click
RequestGET /profiles?region=Europe&interest=hiking
MethodAddressHeadersDataAuthorization
Your ID card rides along:Authorization: Bearer eyJhbGci…
The APIThe one that answers — a server somewhereFirst: is your ID card valid?
Response200 OK · 12 matching profiles
StatusHeadersData
No valid ID card? The answer is 401 Unauthorized — and nothing else comes back.
Your appShows you the 12 profiles
The request is what your app asks for, plus the ID card saying who's asking. The response is what comes back. Every one of the 8 types on the Types of API Calls page is a variation of this same round trip.

The Anatomy of an API Call

Every web-based API call is made up of the same five parts. Click any one of them to see what it does — and notice that part 4, authentication, is the ID card from the flow chart above.

How API Calls Travel Across the Internet

Every API call is a request and a response. That round trip can take three common paths:

1From your browser across the internet to a company's server — like when you click something on a webpage and it loads a list of products.

2From one server to another server owned by the same company, on a private network — like when you buy an item and the company's storefront server sends an API call to its inventory server to deduct the item from stock.

3From Company A's server across the internet to Company B's server — like when an online store sends an API call to a payment processor, which works with the card networks and banks to process your purchase.

The most common way for those web-based API calls to travel is by HTTPS: Hypertext Transfer Protocol Secure. HTTPS is the universal security baseline for the modern web, used whenever a web browser or application needs to securely exchange information with a server.

The Three Pillars of HTTPS 🛡️

Encryption

It scrambles the data being sent — passwords, credit card numbers or API tokens. If someone intercepts the data on the way, it looks like unreadable, chaotic gibberish.

The call leaves your device already scrambled and is only unscrambled at the other end.

Data Integrity

It prevents the data from being subtly changed or corrupted during transit. If a malicious router tries to alter a file or inject a virus into the stream, HTTPS detects it and drops the connection.

What you get back is exactly what the server sent — nothing added along the way.

Authentication

It proves that you are actually talking to the real website or server you intended to reach — that you're connected to the actual openai.com and not a fake look-alike server set up by scammers.

Proved with a certificate issued to that company, checked automatically by your browser.

So when you read an API call's address anywhere on this site — https://company.com/api/v2/customers — that s is the whole point: from the moment the call leaves your device until the answer comes back, it's travelling inside the safe.

Where to Go Next

Keep going in order, or jump to any page from the top menu.