Feb 6 (edited) • General Discussion 💬
What an API actually is?
Most people misunderstand APIs because they zoom in too early 👀
API is the big picture.
HTTP methods are just a small part of it 🧩
GET and POST are not “the API”.
They’re just actions inside an API system.
—
What an API actually is 💡
An API is a structured way for one app to talk to another app
without knowing how it works internally.
You follow the rules.
You get the response.
—
Every API request has 4 core pieces 🧱
1. Endpoint
2. HTTP Method
3. Headers
4. Body
That’s it. Everything else builds on this.
—
Endpoint vs HTTP Method 📍➡️⚙️
Endpoint answers:
Where am I sending the request?
What resource am I dealing with?
Example:
/users
HTTP Method answers:
What action should happen at that address?
Same endpoint, different intent:
GET /users → read
POST /users → create
PUT /users → update
DELETE /users → remove
Address vs action.
—
Headers (instructions, not data) 📨
Headers are metadata.
They are information about the request, not the actual data.
Common ones you’ll see everywhere:
Authorization → who you are 🔐
Content-Type → format of the body
Accept → format of the response
Headers tell the server how to read the message.
—
Body (the actual content) 📦
If headers are instructions,
the body is the content.
Usually present with:
POST → create
PUT / PATCH → update
—
The key link most people miss 🔗
Body = the data
Content-Type = how that data is formatted
No Content-Type → the body is unclear to the server.
—
Real example: creating a user 👇
POST /users
Content-Type: application/json
Body:
{
"name": "Harshad",
}
Translated into plain English:
Create a user at /users.
The data is JSON.
Here is the user information.
—
Once you start seeing APIs as a simple conversation with rules 🗣️
they stop feeling complicated.
11
10 comments
What an API actually is?
skool.com/ai-automation-society
Learn to get paid for AI solutions, regardless of your background.
Leaderboard (30-day)
1
+5730
2
🔥
+4384
3
+3918
4
+2336
5
+885
Powered by