Why Request headers (Content-Type, Accept) in Rest API? - Purpose & Use Cases

The Big Idea

What if your app could talk clearly to servers and never get confused about data again?

The Scenario

Imagine you want to send a letter to a friend, but you don't tell them if it's a birthday card, a recipe, or a photo. They open it confused, not knowing how to read it properly.

In web communication, this is like sending data without telling the server or client what type it is.

The Problem

Without specifying headers like Content-Type or Accept, servers and clients guess the data format. This guessing can cause errors, misunderstandings, or crashes.

Manually handling this guessing is slow and leads to bugs, especially when many data types are involved.

The Solution

Request headers like Content-Type and Accept clearly tell the server what data format is sent and what format is expected back.

This clear communication avoids confusion, speeds up processing, and makes APIs reliable and easy to use.

Before vs After

✗ Before

POST /api/data

{ "name": "Alice" }  # No headers, server guesses format

✓ After

POST /api/data
Content-Type: application/json
Accept: application/json

{ "name": "Alice" }

What It Enables

It enables smooth, error-free data exchange between clients and servers by clearly defining data formats.

Real Life Example

When you upload a photo to a social media app, the Content-Type header tells the server it's an image, and the Accept header tells the app what kind of response to expect, like JSON confirmation.

Key Takeaways

Headers tell servers and clients what data format is sent and expected.

Without them, communication is error-prone and slow.

Using Content-Type and Accept headers makes APIs reliable and clear.

Practice

1. What does the Content-Type header specify in an HTTP request?

easy

A. The format of the data being sent to the server

B. The format of the data the client wants to receive

C. The server's IP address

D. The HTTP method used in the request

Solution

1. Step 1: Understand the role of Content-Type

   The Content-Type header tells the server what format the request body data is in, such as JSON or XML.

2. Step 2: Differentiate from Accept header

   The Accept header tells the server what response format the client wants, not the data sent.

3. Final Answer:

   The format of the data being sent to the server -> Option A

4. Quick Check:

   Content-Type = request data format [OK]

Hint: Content-Type = your data format sent [OK]

Common Mistakes:

• Confusing Content-Type with Accept header
• Thinking Content-Type is about response format
• Ignoring the header completely

2. Which of the following is the correct way to set the Accept header to request JSON data in an HTTP request?

easy

A. Content-Type: application/json

B. Accept: text/html

C. Accept: application/json

D. Content-Type: text/plain

Solution

1. Step 1: Identify the Accept header usage

   The Accept header tells the server what response format the client wants, such as JSON.

2. Step 2: Match the correct MIME type for JSON

   The MIME type for JSON is application/json, so the header should be Accept: application/json.

3. Final Answer:

   Accept: application/json -> Option C

4. Quick Check:

   Accept header for JSON = application/json [OK]

Hint: Accept header = desired response format [OK]

Common Mistakes:

• Using Content-Type instead of Accept for response format
• Using wrong MIME type like text/html for JSON
• Mixing up header names

3. Given this HTTP request snippet:

POST /api/data HTTP/1.1
Host: example.com
Content-Type: application/json
Accept: application/xml

{"name": "Alice"}

What format will the server expect the request body to be, and what format will it try to respond with?

medium

A. Request body XML, response JSON

B. Request body XML, response XML

C. Request body JSON, response JSON

D. Request body JSON, response XML

Solution

1. Step 1: Analyze Content-Type header

   The Content-Type is application/json, so the server expects JSON data in the request body.

2. Step 2: Analyze Accept header

   The Accept header is application/xml, so the client wants the response in XML format.

3. Final Answer:

   Request body JSON, response XML -> Option D

4. Quick Check:

   Content-Type = JSON, Accept = XML [OK]

Hint: Content-Type = sent data, Accept = wanted response [OK]

Common Mistakes:

• Mixing up Content-Type and Accept roles
• Assuming response matches request format
• Ignoring headers and guessing defaults

4. You wrote this HTTP request:

POST /submit HTTP/1.1
Host: example.com
Content-Type: application/json
Accept: application/json

name=John&age=30

Why might the server reject this request or fail to parse the data?

medium

A. Because the HTTP method POST is not allowed

B. Because the Content-Type says JSON but the body is URL-encoded form data

C. Because Accept header is incorrect for JSON

D. Because the Host header is missing

Solution

1. Step 1: Check Content-Type and body format

   The Content-Type is application/json, but the body is name=John&age=30, which is URL-encoded form data, not JSON.

2. Step 2: Understand server parsing behavior

   The server expects JSON data but receives form data, so it may reject or fail to parse the request.

3. Final Answer:

   Because the Content-Type says JSON but the body is URL-encoded form data -> Option B

4. Quick Check:

   Content-Type must match body format [OK]

Hint: Match Content-Type with actual body format [OK]

Common Mistakes:

• Ignoring mismatch between Content-Type and body
• Assuming Accept header affects request body
• Thinking Host header is missing when it is present

5. You want to send JSON data to an API and receive a JSON response. Which headers should you set correctly in your HTTP request to ensure this communication?

hard

A. Content-Type: application/json and Accept: application/json

B. Content-Type: text/plain and Accept: application/json

C. Content-Type: application/json and Accept: text/html

D. Content-Type: application/xml and Accept: application/json

Solution

1. Step 1: Set Content-Type for request data

   Since you are sending JSON data, set Content-Type: application/json so the server knows the format of the data you send.

2. Step 2: Set Accept for response format

   To receive JSON response, set Accept: application/json to tell the server you want JSON back.

3. Final Answer:

   Content-Type: application/json and Accept: application/json -> Option A

4. Quick Check:

   Both headers set to application/json for JSON exchange [OK]

Hint: Both headers must match JSON for send and receive [OK]

Common Mistakes:

• Setting Content-Type and Accept to different formats
• Using text/plain or XML when JSON is needed
• Forgetting to set Accept header