Day 27 of #100DaysOfCode — REST API

Whether you realize it or not, you’ve already been using REST APIs every time an app sends a request and receives a response. Your weather app, your social feeds, your login screen — they’re all quietly talking to servers through REST APIs in the background. Today, on Day 27, I focused on truly understanding how the request–response cycle works behind the scenes. What Is a REST API? Think of a REST API like a waiter in a restaurant : You (the client/app) request food. The kitchen (server/database) prepares it. The waiter (REST API) takes your request, delivers it, and brings the result back. You never go into the kitchen. You communicate only through the waiter — using standard, agreed-upon phrases. 🔍 So What Is REST? REST (Representational State Transfer) is a set of rules that allow two applications to communicate over the internet. The client uses standard HTTP methods to talk to a server and fetch or change data. Core HTTP Methods in REST APIs Here are the most common ones: Method