Raw body (text, XML) in Postman

Introduction

Raw body lets you send exact text or XML data in your API requests. This helps test how the server handles specific input formats.

You want to send plain text data to an API, like a message or note.

You need to test an API that accepts XML formatted data.

You want to simulate sending custom payloads that are not JSON or form data.

You are testing how the server processes raw text inputs.

You want to check if the API correctly parses XML requests.

Syntax

Postman

POST /api/example HTTP/1.1
Host: example.com
Content-Type: text/plain

Your raw text data here

Set the Content-Type header to match your raw data type (e.g., text/plain or application/xml).

In Postman, select 'raw' in the Body tab and choose the data format from the dropdown.

Examples

Sends plain text as the request body.

Postman

POST /api/message HTTP/1.1
Host: example.com
Content-Type: text/plain

Hello, this is a plain text message.

Sends XML data as the request body.

Postman

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

<note><to>User</to><message>Hello XML</message></note>

Sample Program

This request sends an XML order to the server. The server should parse the XML and respond accordingly.

Postman

POST /api/submit HTTP/1.1
Host: example.com
Content-Type: application/xml

<order><id>123</id><item>Book</item></order>

Important Notes

Always match the Content-Type header with the raw data format you send.

Raw body is useful when APIs do not accept JSON or form data.

Use Postman's preview or response tabs to verify the server's reply.

Summary

Raw body lets you send exact text or XML in API requests.

Set the correct Content-Type header to help the server understand your data.

Use raw body to test APIs that expect plain text or XML inputs.

Practice

1. What is the main purpose of using the Raw body option in Postman when testing APIs?

easy

A. To send exact text or XML data as the request body

B. To automatically generate JSON data for the request

C. To create a graphical interface for the API

D. To validate the response status code

Solution

1. Step 1: Understand Raw Body usage

   The Raw body option allows sending exact text or XML data in the request body without modification.

2. Step 2: Compare with other options

   Other options like form-data or JSON editor do not send plain text or XML exactly as typed.

3. Final Answer:

   To send exact text or XML data as the request body -> Option A

4. Quick Check:

   Raw body = exact text/XML data [OK]

Hint: Raw body sends exact text or XML as is [OK]

Common Mistakes:

• Confusing raw body with JSON auto-formatting
• Thinking raw body generates data automatically
• Using raw body to validate response codes

2. Which Content-Type header should you set in Postman when sending XML data in the Raw body?

easy

A. application/json

B. text/plain

C. multipart/form-data

D. application/xml

Solution

1. Step 1: Identify correct Content-Type for XML

   XML data requires the Content-Type header to be application/xml so the server knows to parse XML.

2. Step 2: Eliminate other options

   application/json is for JSON, text/plain is plain text, and multipart/form-data is for file uploads.

3. Final Answer:

   application/xml -> Option D

4. Quick Check:

   XML Content-Type = application/xml [OK]

Hint: Use application/xml header for XML raw body [OK]

Common Mistakes:

• Using application/json for XML data
• Omitting Content-Type header
• Choosing text/plain for XML

3. Given this XML raw body sent in Postman:

<note>
  <to>Alice</to>
  <from>Bob</from>
  <message>Hello</message>
</note>

What will the server receive if the Content-Type is correctly set to application/xml?

medium

A. Plain text without any tags

B. A JSON object with keys 'to', 'from', and 'message'

C. The exact XML text as shown, including tags and content

D. An error because XML is not supported

Solution

1. Step 1: Understand raw body with XML and Content-Type

   When raw XML is sent with Content-Type application/xml, the server receives the exact XML text including tags.

2. Step 2: Eliminate other options

   The server does not convert XML to JSON automatically, nor strip tags or throw errors if XML is supported.

3. Final Answer:

   The exact XML text as shown, including tags and content -> Option C

4. Quick Check:

   Raw XML + application/xml = exact XML text [OK]

Hint: Raw XML with correct header sends exact XML text [OK]

Common Mistakes:

• Assuming XML converts to JSON automatically
• Thinking tags are removed in transmission
• Believing server errors without checking support

4. You send this raw XML in Postman:

<user>
  <name>John</name>
  <age>30</age>
</user>

But the server returns a 400 Bad Request error. What is the most likely cause?

medium

A. The XML tags are invalid and malformed

B. Content-Type header is missing or incorrect

C. Raw body cannot send XML data

D. Postman does not support sending raw bodies

Solution

1. Step 1: Check XML validity

   The XML tags are well-formed and valid, so the XML itself is not the issue.

2. Step 2: Consider Content-Type header

   If the Content-Type header is missing or not set to application/xml, the server may reject the request with 400 error.

3. Final Answer:

   Content-Type header is missing or incorrect -> Option B

4. Quick Check:

   Missing/incorrect Content-Type causes 400 error [OK]

Hint: Always set Content-Type for XML raw body [OK]

Common Mistakes:

• Blaming XML syntax without checking header
• Thinking raw body cannot send XML
• Assuming Postman lacks raw body support

5. You want to test an API that accepts plain text commands in the raw body. Which combination in Postman is correct to send the command START successfully?

hard

A. Set raw body to START and Content-Type to text/plain

B. Set raw body to {"command":"START"} and Content-Type to application/json

C. Set raw body to <command>START</command> and Content-Type to application/xml

D. Set raw body to START and Content-Type to application/xml

Solution

1. Step 1: Identify data type expected by API

   The API expects plain text commands, so raw body should contain plain text like START.

2. Step 2: Set matching Content-Type header

   For plain text, the Content-Type must be text/plain to inform the server correctly.

3. Final Answer:

   Set raw body to START and Content-Type to text/plain -> Option A

4. Quick Check:

   Plain text command needs text/plain header [OK]

Hint: Match raw body content with correct Content-Type header [OK]

Common Mistakes:

• Sending plain text with JSON or XML headers
• Wrapping plain text in JSON or XML tags unnecessarily
• Using wrong Content-Type for plain text