Raw body (text, XML) in Postman - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to set the raw body type to XML in Postman.

Postman

pm.request.body.mode = '[1]';

Drag options to blanks, or click blank then click option'

Araw

Bjson

Cformdata

Durlencoded

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'json' instead of 'raw' for XML raw body.

Setting mode to 'formdata' or 'urlencoded' which are not raw XML.

Setting pm.request.body.mode to raw tells Postman to use raw as the body type for XML content.

2fill in blank

medium

Complete the code to set the raw XML body content in Postman.

Postman

pm.request.body.raw = '[1]';

Drag options to blanks, or click blank then click option'

A<note><to>User</to></note>

B{"note": "User"}

Cto=User&from=Admin

D<note to='User'></note>

Attempts:

3 left

💡 Hint

Common Mistakes

Using JSON format instead of XML.

Using URL encoded string instead of raw XML.

The raw body content must be a string containing valid XML. Option A is a valid XML string.

3fill in blank

hard

Fix the error in setting the Content-Type header for XML raw body in Postman.

Postman

pm.request.headers.upsert({ key: 'Content-Type', value: '[1]' });

Drag options to blanks, or click blank then click option'

Amultipart/form-data

Bapplication/xml

Capplication/json

Dtext/plain

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'application/json' for XML body.

Using 'text/plain' which is generic and not specific to XML.

The correct Content-Type for XML raw body is application/xml.

4fill in blank

hard

Fill both blanks to correctly set raw XML body and Content-Type header in Postman.

Postman

pm.request.body.mode = '[1]';
pm.request.headers.upsert({ key: 'Content-Type', value: '[2]' });

Drag options to blanks, or click blank then click option'

Axml

Bapplication/json

Capplication/xml

Draw

Attempts:

3 left

💡 Hint

Common Mistakes

Mismatch between body mode and Content-Type header.

Using 'application/json' header for XML body.

Set the body mode to 'raw' and Content-Type header to 'application/xml' for XML raw body.

5fill in blank

hard

Fill all three blanks to create a Postman test that checks if the response Content-Type is XML.

Postman

pm.test('Response is XML', () => {
  pm.response.to.have.header('[1]');
  pm.expect(pm.response.headers.get('[2]')).to.include('[3]');
});

Drag options to blanks, or click blank then click option'

AContent-Type

Capplication/xml

DAccept

Attempts:

3 left

💡 Hint

Common Mistakes

Checking wrong header like 'Accept'.

Checking for 'application/json' instead of 'application/xml'.

The test checks that the response has a 'Content-Type' header and that its value includes 'application/xml'.

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