Client
API
API Contract
Client asks. API responds. Your UI updates.
Think of methods as CRUD actions: Create, Read, Update, Delete.

HTTP Methods Are Verbs

Methods describe intent. Same endpoint, different method, different behavior. This keeps APIs predictable and easier to maintain.

GET Reads Data

GET fetches data without changing server state. It should be safe to repeat.

POST Creates Data

POST usually creates new resources. Repeating the same POST can create duplicates if your API is not idempotent.

PATCH Updates Part of a Resource

PATCH modifies only selected fields, like changing a user email without replacing the entire user object.

DELETE Removes Data

DELETE requests remove resources. Usually no payload comes back, just a success status like 204.

Method + Status = Story

Read method and status together: POST + 201 means created, DELETE + 204 means removed, GET + 304 means cache still valid.

Methods Mapped

You now know how to express read/write intent correctly so backend contracts stay clean and frontend behavior stays predictable.

Next: Status CodesBack to APIs Menu
AlgoAnimator: Interactive Data Structures