x-www-form-urlencoded body in Postman - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the x-www-form-urlencoded body format?

It is a way to send data in HTTP requests where key-value pairs are encoded in the URL format, like key1=value1&key2=value2. It is commonly used in HTML forms and APIs.

beginner

How does Postman send data when you select x-www-form-urlencoded in the body tab?

Postman encodes the keys and values as URL-encoded strings and sends them in the request body with the header Content-Type: application/x-www-form-urlencoded.

intermediate

Why do spaces become + or %20 in x-www-form-urlencoded data?

Spaces are not allowed in URLs, so they are encoded as + or %20 to make the data safe to send over HTTP.

intermediate

What is the difference between application/x-www-form-urlencoded and multipart/form-data?

application/x-www-form-urlencoded sends data as URL-encoded key-value pairs, good for simple text data. multipart/form-data is used for files or binary data and sends data in parts.

beginner

How can you test an API that expects x-www-form-urlencoded data in Postman?

Select POST or PUT method, go to the Body tab, choose x-www-form-urlencoded, enter key-value pairs, then send the request. Check the response to verify the API works as expected.

What header does Postman set automatically when you use x-www-form-urlencoded body?

A Content-Type: text/plain

B Content-Type: application/x-www-form-urlencoded

C Content-Type: multipart/form-data

D Content-Type: application/json

The x-www-form-urlencoded body format requires the Content-Type header to be set to application/x-www-form-urlencoded.

In x-www-form-urlencoded data, how are spaces encoded?

A _

B -

C %25

D %20 or +

Spaces are encoded as + or %20 in URL-encoded data to be safely transmitted.

Which HTTP method is commonly used with x-www-form-urlencoded body?

A POST

B GET

C DELETE

D HEAD

POST is commonly used to send x-www-form-urlencoded data in the request body.

What is a key limitation of x-www-form-urlencoded compared to multipart/form-data?

A Cannot send files

B Cannot send text

C Cannot send numbers

D Cannot send URLs

x-www-form-urlencoded cannot send files or binary data, unlike multipart/form-data.

In Postman, where do you enter key-value pairs for x-www-form-urlencoded data?

A Params tab

B Headers tab

C Body tab under x-www-form-urlencoded

D Authorization tab

You enter key-value pairs in the Body tab when x-www-form-urlencoded is selected.

Explain how x-www-form-urlencoded data is formatted and sent in an HTTP request.

Think about how form data looks in a URL and how it is included in the request.

Describe the steps to test an API endpoint that requires x-www-form-urlencoded data using Postman.

Imagine you are filling out a form and sending it to the server.

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