PART 2: REST APIs (The Real Game)

Great 👍
Here is PART 2 – REST APIs, written in the same ultra-easy, 80–20, beginner-first style:
👉 real websites, real thinking, minimum words, maximum clarity, emojis everywhere.

---

📘 Web API — Part 2

REST APIs (The Real Game – 80–20)

---

🌍 INTRO: Why REST Exists (Real Life First)

🤔 Problem before REST

Earlier:

• Different rules for every API ❌

• XML, SOAP, heavy formats ❌

• Hard to understand & slow ❌

💡 REST fixed this

REST gave simple rules so that:

• Any developer can understand any API

• Any language can talk to any server

📌 That’s why 90% APIs today are REST APIs

---

🧠 What is REST? (One-Line)

REST is a way to design APIs using simple URLs, HTTP methods, and JSON.

---

🏢 Real Websites Using REST

Website	REST Example
Naukri	/jobs, /companies
Amazon	/products, /orders
Paytm	/payments, /transactions
Instagram	/users, /posts

📌 If URL looks clean → mostly REST API

---

🔑 Core Idea of REST (Think in NOUNS)

❌ Not this:

/getJobs
/addJob
/deleteJob

✅ This:

/jobs
/jobs/123

👉 REST thinks in resources (nouns)
👉 Actions come from HTTP methods

---

1️⃣ Resources & Endpoints (Most Important)

📦 Resource = Data Thing

• users

• jobs

• products

• orders

🔗 Endpoint = URL of resource

/api/jobs

---

🧾 REST CRUD Mapping

Action	Method	Endpoint
Read all	GET	/jobs
Read one	GET	/jobs/5
Create	POST	/jobs
Update	PUT	/jobs/5
Delete	DELETE	/jobs/5

📌 Same URL, different method = different action

---

2️⃣ Stateless APIs (Simple Meaning)

🧠 Stateless = Server doesn’t remember you

Each request must have:

• All required data

• Authentication token

❌ Server memory
✅ Client responsibility

---

🏧 ATM Example

Every time you:

• Insert card 💳

• Enter PIN 🔐

ATM doesn’t remember you from last time.

👉 That’s REST

---

3️⃣ JSON as Default Language

REST APIs mostly use JSON.

📦 Example Response

{
  "job": "UP Police",
  "salary": 81000,
  "location": "Bihar"
}

📌 Human-readable
📌 Language-independent
📌 Fast

---

4️⃣ Designing Clean REST URLs

❌ Bad URLs

/getAllJobs
/deleteJobById

✅ Good REST URLs

/jobs
/jobs/12

---

📌 URL Rules (Remember These Only)

Rule	Example
Use nouns	/jobs
Use plural	/users
No verbs	❌ /getUsers
Use ID	/jobs/5

---

5️⃣ Path Params vs Query Params (Crystal Clear)

📍 Path Param → Specific item

/jobs/10

👉 Job ID = 10

---

🔍 Query Param → Filter/search

/jobs?city=patna&salary=50000

👉 Search jobs

---

🧠 Thumb Rule

• Path = “Which one?”

• Query = “Filter it”

---

6️⃣ Pagination, Filtering & Sorting (Real World)

📚 Pagination (Big Data Handling)

/jobs?page=1&limit=10

📌 Never return 10,000 records ❌
📌 Always paginate ✅

---

🔍 Filtering

/jobs?state=bihar

---

🔃 Sorting

/jobs?sort=salary_desc

---

7️⃣ API Versioning (Life Saver)

🤕 Problem

If API changes → old apps break ❌

💊 Solution

Version your API

---

✅ Simple Versioning

/api/v1/jobs
/api/v2/jobs

📌 This is enough for 80% cases

---

🧠 Complete Real-Life REST Example

🎯 Case: Job Listing Website

🔗 Request

GET /api/v1/jobs?city=patna&page=1

---

📦 Response

{
  "page": 1,
  "total": 120,
  "data": [
    {
      "title": "UP Police",
      "salary": 81000
    }
  ]
}

---

🎨 Frontend shows:

• Job name

• Salary

• Location

User clicks → applies 💼😊

---

⚠️ Common REST Mistakes (Avoid These)

❌ Verbs in URLs
❌ No pagination
❌ No versioning
❌ Inconsistent naming

---

🧠 PART 2 – ONE-PAGE SUMMARY (80–20)

• REST = design style, not technology

• Resources = nouns

• HTTP methods = actions

• URLs must be clean

• JSON everywhere

• Version your API

---

🚀 After Part 2, You Can:

✔ Design clean APIs
✔ Read any REST API doc
✔ Avoid beginner mistakes
✔ Prepare for interviews

---

🔜 Coming Next (Part 3)

CRUD + Database (Real Job Skill)
👉 Create, update, delete data
👉 API + DB flow
👉 Real-world examples

Say “Next Part” and we continue 🔥