What is the difference between Content-Type and Accept headers?
PICTURE THIS: A REST CALL
Simple meaning
Content-Type describes the body you are sending, such as application/json.
WHY — HTTP instead of guessing?
Why interviewers care about HTTP:
contrast on HTTP, not two memorised paragraphs.
the developer, then one case where picking wrong hurts.
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:
- 1Content-Type describes the body
you are sending, such as application/json.
- 2Accept tells the server
which response formats the client can handle.
- 3A MERN API should
reject unsupported Content-Type values instead of silently ignoring the body.
- 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
Content-Type describes the body you are sending, such as application/json. Accept tells the server which response formats the client can handle.