x-www-form-urlencoded body in Postman - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to set the Content-Type header for an x-www-form-urlencoded request in Postman.

Postman

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

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

Amultipart/form-data

Bapplication/x-www-form-urlencoded

Ctext/plain

Dapplication/json

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'application/json' instead of 'application/x-www-form-urlencoded'.

Forgetting to set the Content-Type header.

The Content-Type header must be set to application/x-www-form-urlencoded to send data in this format.

2fill in blank

medium

Complete the code to add a key-value pair to the x-www-form-urlencoded body in Postman.

Postman

pm.request.body.urlencoded.add({ key: '[1]', value: 'testValue' });

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

AAuthorization

BContent-Type

Cusername

DAccept

Attempts:

3 left

💡 Hint

Common Mistakes

Using header names like 'Content-Type' as form keys.

Leaving the key empty.

When adding form data, the key should be the name of the form field, like 'username'.

3fill in blank

hard

Fix the error in the code to correctly clear all existing x-www-form-urlencoded body parameters in Postman.

Postman

pm.request.body.urlencoded.[1]();

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

Aclear

BremoveAll

CdeleteAll

Dreset

Attempts:

3 left

💡 Hint

Common Mistakes

Using non-existent methods like 'removeAll' or 'deleteAll'.

Trying to assign an empty array instead of calling a method.

The correct method to clear all parameters is clear().

4fill in blank

hard

Fill both blanks to correctly update the value of a key in the x-www-form-urlencoded body in Postman.

Postman

const param = pm.request.body.urlencoded.find(item => item.key === '[1]');
if (param) { param.value = '[2]'; }

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

AsessionId

Btoken

C12345

Dabcdef

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up keys and values.

Using a numeric value when a string is expected.

We look for the key 'sessionId' and update its value to 'abcdef'.

5fill in blank

hard

Fill all three blanks to create a new x-www-form-urlencoded body with two parameters in Postman.

Postman

pm.request.body.update({
  mode: '[1]',
  urlencoded: [
    { key: '[2]', value: 'value1' },
    { key: '[3]', value: 'value2' }
  ]
});

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

Aurlencoded

Bemail

Cpassword

Dformdata

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'formdata' mode instead of 'urlencoded'.

Using incorrect keys that don't match form fields.

The mode must be 'urlencoded' to send form data. The keys are 'email' and 'password' as typical form fields.

Practice

1. What does the x-www-form-urlencoded body type do in Postman?

easy

A. Sends data as plain text without encoding

B. Sends data as a JSON object in the request body

C. Uploads files as binary data

D. Sends form data as key-value pairs joined by '&' in the request body

Solution

1. Step 1: Understand the body type purpose

   x-www-form-urlencoded sends form data as key-value pairs joined by '&' in the request body, similar to how HTML forms send data.

2. Step 2: Compare with other body types

   JSON body sends data as JSON, binary uploads files, and plain text sends raw text. Only x-www-form-urlencoded uses key-value pairs joined by '&'.

3. Final Answer:

   Sends form data as key-value pairs joined by '&' in the request body -> Option D

4. Quick Check:

   Form data = key-value pairs & joined by '&' [OK]

Hint: Remember: form data uses key=value pairs joined by & [OK]

Common Mistakes:

• Confusing x-www-form-urlencoded with JSON body
• Thinking it uploads files
• Assuming it sends raw text without encoding

2. Which of the following is the correct way to set a key-value pair in Postman's x-www-form-urlencoded body tab?

easy

A. key: value

B. key=value

C. key and value in separate columns

D. JSON format like {"key":"value"}

Solution

1. Step 1: Check Postman UI for x-www-form-urlencoded

   In Postman, the x-www-form-urlencoded body tab shows two columns: one for keys and one for values.

2. Step 2: Understand correct input format

   You enter keys and values separately in these columns; Postman encodes them automatically as key=value pairs joined by '&'.

3. Final Answer:

   key and value in separate columns -> Option C

4. Quick Check:

   Separate columns = correct input method [OK]

Hint: Use separate key and value columns in Postman body tab [OK]

Common Mistakes:

• Typing key and value together with ':' or '=' manually
• Trying to enter JSON in x-www-form-urlencoded tab
• Not using the provided columns for input

3. Given the following key-value pairs in Postman's x-www-form-urlencoded body:
username: user1
password: pass@123
What will be the encoded request body sent?

medium

A. username=user1&password=pass%40123

B. username=user1,password=pass@123

C. {"username":"user1","password":"pass@123"}

D. username:user1&password:pass@123

Solution

1. Step 1: Understand URL encoding in x-www-form-urlencoded

   Special characters like '@' are percent-encoded. '@' becomes '%40'. Keys and values are joined by '=', pairs joined by '&'.

2. Step 2: Apply encoding to given data

   username=user1 (no special chars), password=pass@123 becomes password=pass%40123. Joined as username=user1&password=pass%40123.

3. Final Answer:

   username=user1&password=pass%40123 -> Option A

4. Quick Check:

   Special chars encoded, pairs joined by & [OK]

Hint: Encode special chars like '@' as %40 in form data [OK]

Common Mistakes:

• Not encoding special characters
• Using JSON format instead of form encoding
• Using commas or colons instead of & and =

4. You set the x-www-form-urlencoded body in Postman with keys and values, but the server responds with a 400 Bad Request error. What is the most likely cause?

medium

A. You forgot to set the Content-Type header to application/x-www-form-urlencoded

B. You used JSON format in the body tab

C. You entered keys and values in separate columns

D. You used GET method instead of POST

Solution

1. Step 1: Check Content-Type header requirement

   When sending x-www-form-urlencoded data, the Content-Type header must be set to application/x-www-form-urlencoded so the server knows how to parse the body.

2. Step 2: Analyze common mistakes

   Using JSON format or entering keys correctly is fine if Content-Type is correct. Using GET method sends no body. The most common cause is missing or wrong Content-Type header.

3. Final Answer:

   You forgot to set the Content-Type header to application/x-www-form-urlencoded -> Option A

4. Quick Check:

   Content-Type header missing = 400 error [OK]

Hint: Always set Content-Type header for form data [OK]

Common Mistakes:

• Not setting Content-Type header
• Using wrong HTTP method
• Entering data in wrong format

5. You want to send a login request using x-www-form-urlencoded body in Postman with keys username and password. The password contains spaces and special characters like pass word@123!. How should you prepare the body to ensure the server receives it correctly?

hard

A. Manually replace spaces with '%20' and special chars with percent codes before entering

B. Enter keys and values normally; Postman will encode spaces as '+' and special chars automatically

C. Use JSON body instead to avoid encoding issues

D. Replace spaces with underscores and remove special characters manually

Solution

1. Step 1: Understand Postman's encoding behavior

   Postman automatically encodes spaces as '+' and special characters as percent-encoded values when using x-www-form-urlencoded body type.

2. Step 2: Avoid manual encoding

   Manually encoding or altering the data can cause errors or double encoding. Using JSON body changes the content type and server parsing. Replacing characters manually is error-prone.

3. Final Answer:

   Enter keys and values normally; Postman will encode spaces as '+' and special chars automatically -> Option B

4. Quick Check:

   Postman auto-encodes form data correctly [OK]

Hint: Let Postman handle encoding; enter raw values normally [OK]

Common Mistakes:

• Manually encoding values causing double encoding
• Switching to JSON body unnecessarily
• Altering data by removing or replacing characters