The 8 Types of API Calls

Different jobs needed different delivery methods, so each type was invented to fix a specific problem — and they're listed in the order they came out, oldest first. Click a name to jump to its example, or open When It Came Out and What Did It Improve to see why each one exists.

Timeline: When Each API Call Came Out & Why

  1. 1980sRPC

    Companies split one enormous program across separate servers (billing here, customer records there), and those machines needed a way to ask each other for things.

  2. Late 1990sSOAP

    Big companies, banks and governments needed one strict, documented contract so very different systems could talk safely — the same server-to-server wave as RPC.

  3. 1999AJAX

    Web pages had to stop reloading for every single click, so they started fetching just the new piece.

  4. 2000REST API

    Phones and web apps needed far less data, which brought simple addresses and lighter replies.

  5. 2007Webhooks

    Some things can't wait for the next ask, so the other side pushes a message to you the moment something happens.

  6. 2011WebSockets

    Chat and live updates needed a line left open both ways, so either side can talk instantly.

  7. 2012GraphQL

    Mobile apps needed to ask for exactly the fields they want — nothing more — to save data.

  8. 2020OpenAI API

    AI became something you simply call, instead of something you build yourself.

None of them replaced the last one — they stacked. The app you open next is using most of them at once.

Source: Why Does the World Have — and Need — API Calls? — Mountain Chick Designs

01 · 1980s

RPC

Example
Run a function on another computer

Remote Procedure Call — one program calls a named function that lives on another server as if it were local. Common between a company's own internal services (gRPC is a popular form).

02 · Late 1990s

SOAP

Example
Strict, formal XML messages

Simple Object Access Protocol — an older, highly structured standard that wraps every request in a formal XML “envelope” with strict rules for security and format.

03 · 1999

AJAX

Example
Update part of a page without reloading

Asynchronous JavaScript and XML — a technique where the browser sends an API call in the background and updates just one part of the page with the result. The whole page never reloads.

04 · 2000

REST API

Example
Ask for a resource at a web address

The most common API call. The app asks the server for something at a specific web address (URL) using a method like GET (read), POST (create), PUT (update) or DELETE (remove).

05 · 2007

Webhooks

Example
The server calls you when something happens

A reverse API call. Instead of your app constantly checking, the server automatically sends a message to a pre-registered address the moment an event happens.

06 · 2011

WebSockets

Example
Keep a live two-way line open

A connection that stays open between your browser and the server. Either side can send messages at any moment, so new information appears instantly without asking again.

07 · 2012

GraphQL

Example
Ask for exactly the fields you need

A query language for APIs. Instead of many fixed URLs, the app sends one query describing exactly which pieces of data it wants, and the server returns only those pieces.

08 · 2020

OpenAI API

Example
Send a request to an AI model

An AI API (built on REST) where the app sends a natural-language prompt plus context to a large language model and gets back an intelligent, written answer.

Examples: Request, Response & Why

Each example happens inside DuckBuddy, a social platform for remote workers. Every example starts closed — click one to open its request, its response and why it's used.

Before you read them: who is calling whom?

  • A customer's device → the company's server — out over the public internet. It starts with a tap, a search or a page load, carries the customer's login token, and has to travel by HTTPS.REST · AJAX · GraphQL · WebSockets
  • One company's server → another company's server — usually across the public internet as well, but between two backends rather than a browser. Nobody is watching a screen; an event or a schedule triggers the call.SOAP payments · webhooks · AI calls
  • Inside one company's own network — never touches the public internet at all. Private, very fast, and completely invisible to customers.RPC · the behind-the-scenes hop in every other type

Most features use all three at once: your phone calls DuckBuddy over the internet, DuckBuddy's servers call each other privately, and one of them calls the bank. Each example below now says which route its call takes.

How They Work Together

In a modern platform these technologies combine to feel fast and intelligent for the customer.

REST + GraphQL + AJAXSmooth browsing and searching
WebSocketsLive chat & video
WebhooksInstant notifications
OpenAI APIThe smart DuckBuddy Agent

See It on One Page

Below is an example of a DuckBuddy profile page showing an example of each of the different API calls. This is how other webpages and social networking platforms use API calls as well.

Click on an API call to read the definition!

DuckBuddySearch: developers in Europe who love hiking 🔔 3

Live chat: Digital Nomads in Spain

Marco: Welcome! Anyone in Madrid?

Anna: Hola from Valencia!

Sofia is typing…

Type a message…

Where to Go Next

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