RPC
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).
Eight types, in the order they were invented — when each came out, what it improved, and a real request and response for every one of them.
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.
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.
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.
Web pages had to stop reloading for every single click, so they started fetching just the new piece.
Phones and web apps needed far less data, which brought simple addresses and lighter replies.
Some things can't wait for the next ask, so the other side pushes a message to you the moment something happens.
Chat and live updates needed a line left open both ways, so either side can talk instantly.
Mobile apps needed to ask for exactly the fields they want — nothing more — to save data.
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
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).
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.
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.
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).
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.
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.
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.
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.
In a modern platform these technologies combine to feel fast and intelligent for the customer.
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!
Marco: Welcome! Anyone in Madrid?
Anna: Hola from Valencia!
Sofia is typing…
Keep going in order, or jump to any page from the top menu.