Why body format matches API expectations in Postman - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why is JSON body format important in API testing?

When sending a request body in Postman, why must the JSON format match the API expectations exactly?

A Because Postman only accepts JSON bodies and rejects other formats automatically.

B Because the API ignores the body if the JSON format is incorrect but still returns success.

C Because JSON format makes the request faster regardless of API requirements.

D Because the API uses the JSON structure to parse and process the data correctly.

💡 Hint

Think about how the API reads the data you send.

The API expects data in a specific JSON structure to parse it correctly. If the format is wrong, the API cannot understand the data and may return errors.

❓ Predict Output

intermediate

What is the API response when JSON body keys are missing?

Given this API expects a JSON body with keys username and password. What response will the API return if the body is {"username": "user1"}?

A {"error": "Missing password field"}

B {"success": true}

C {"error": "Invalid JSON format"}

D {"error": "User not found"}

💡 Hint

Consider what happens if required fields are missing in the JSON body.

The API checks for required fields. If password is missing, it returns an error indicating the missing field.

❓ assertion

advanced

Which Postman test script correctly asserts the response body format?

Choose the Postman test script that correctly checks if the response JSON has a status key with value success.

A pm.test('Status is success', () => { pm.expect(pm.response.body.status).to.equal('success'); });

B pm.test('Status is success', () => { pm.expect(pm.response.json().status).to.eql('success'); });

C pm.test('Status is success', () => { pm.expect(pm.response.json.status).to.eql('success'); });

D pm.test('Status is success', () => { pm.expect(pm.response.status).to.eql('success'); });

💡 Hint

Remember how to parse JSON response in Postman test scripts.

Use pm.response.json() to parse the response body as JSON. Then check the status key value.

🔧 Debug

advanced

Why does this Postman request fail with 400 Bad Request?

Given this request body in Postman:

{
  "user": "test",
  "pass": "1234"
}

The API expects keys username and password. Why does the request fail?

A Because the JSON keys do not match the API expected keys, causing validation failure.

B Because the JSON body is missing a closing brace causing syntax error.

C Because Postman does not send the body when keys are different from API expectations.

D Because the API only accepts XML format, not JSON.

💡 Hint

Check if the keys in the JSON body match what the API expects.

The API validates the JSON keys strictly. If keys differ, it returns 400 Bad Request due to invalid input.

❓ framework

expert

How to automate validation of JSON body format in Postman Collection Runner?

Which approach best automates checking that the request body matches the API's expected JSON schema during Postman Collection runs?

A Add a pre-request script that modifies the request body to match the expected JSON schema automatically.

B Manually check the request body format before running the collection to ensure it matches the API expectations.

C Use a JSON schema validation test script in Postman that runs after each request to verify the request body matches the schema.

D Use Postman's built-in 'Body Format Checker' feature that automatically fixes JSON body format errors.

💡 Hint

Think about how to validate JSON structure automatically after requests.

Postman allows adding test scripts that validate response or request bodies against JSON schemas. This helps automate format validation during collection runs.