What are the main HTTP methods used in REST APIs?
PICTURE THIS: A REST CALL
Simple meaning
GET reads a resource, POST creates one, PUT replaces one, PATCH updates part of one, and DELETE removes one.
WHY — HTTP instead of guessing?
Why interviewers care about HTTP:
who only read docs from people who shipped.
and tied to Full Stack work.
Name the idea, why it exists, then one short example.
End with when you use it and one common pitfall.
STEPS — What happens step by step?
Before you speak the answer, walk the interviewer through these steps:
- 1GET reads a resource,
POST creates one, PUT replaces one, PATCH updates part of one, and DELETE removes one.
- 2Methods should match intent
so caches, proxies, and clients behave correctly.
- 3GET is treated as
safe and should not change server state.
- 4Give an example
One tiny concrete case you can say aloud.
- 5Common mistake
What juniors usually get wrong.
- 6Close
When you pick this over the alternative.
EXAMPLE — See it in action
Here's a short line you can speak, broken into clear beats:
Note: Adapt this scaffold to your own project — keep it under 60–90 seconds.
Key takeaway
GET reads a resource, POST creates one, PUT replaces one, PATCH updates part of one, and DELETE removes one. Methods should match intent so caches, proxies, and clients behave correctly.