GET request in Postman - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to send a GET request to the URL.

Postman

pm.sendRequest({ url: '[1]', method: 'GET' }, function (err, res) { pm.expect(err).to.be.null; });

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

A'https://api.example.com/data'

B'POST'

C'https://api.example.com/post'

D'DELETE'

Attempts:

3 left

💡 Hint

Common Mistakes

Using HTTP methods like 'POST' or 'DELETE' instead of the URL string.

Not putting the URL inside quotes.

The URL must be a valid string for the GET request. Option A is the correct URL string.

2fill in blank

medium

Complete the code to check the response status is 200.

Postman

pm.sendRequest('https://api.example.com/data', function (err, res) { pm.expect(res.status).to.equal([1]); });

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

A404

B200

C500

D201

Attempts:

3 left

💡 Hint

Common Mistakes

Using 404 which means not found.

Using 500 which means server error.

Status code 200 means the GET request was successful.

3fill in blank

hard

Fix the error in the code to correctly parse JSON response body.

Postman

pm.sendRequest('https://api.example.com/data', function (err, res) { let data = res.[1](); pm.expect(data).to.be.an('object'); });

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

Aparse

Btext

Cbody

Djson

Attempts:

3 left

💡 Hint

Common Mistakes

Using text() returns raw text, not parsed JSON.

Trying to access body() which is not a method.

The method json() parses the response body as JSON.

4fill in blank

hard

Fill both blanks to check the response has a JSON property 'name' with value 'John'.

Postman

pm.sendRequest('https://api.example.com/user', function (err, res) { let data = res.[1](); pm.expect(data).to.have.property('[2]', 'John'); });

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

Ajson

Btext

Cname

Dage

Attempts:

3 left

💡 Hint

Common Mistakes

Using text() instead of json().

Checking wrong property like 'age' instead of 'name'.

Use json() to parse the response and check the property 'name'.

5fill in blank

hard

Fill all three blanks to send a GET request, parse JSON, and assert the 'status' is 'success'.

Postman

pm.sendRequest({ url: [1], method: '[2]' }, function (err, res) { let result = res.[3](); pm.expect(result.status).to.equal('success'); });

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

A'https://api.example.com/status'

BGET

Cjson

DPOST

Attempts:

3 left

💡 Hint

Common Mistakes

Using POST method instead of GET.

Not parsing JSON before accessing properties.

Using wrong URL or missing quotes.

The URL is the API endpoint, method is GET, and json() parses the response.

Practice

1. What is the main purpose of a GET request in Postman?

easy

A. To delete data from the server

B. To retrieve data from a server without changing it

C. To update existing data on the server

D. To send data to a server to create a new resource

Solution

1. Step 1: Understand HTTP methods

   GET requests are designed to fetch or retrieve data from a server without modifying it.

2. Step 2: Compare with other methods

   POST creates, PUT updates, DELETE removes data, so they are not for just retrieving data.

3. Final Answer:

   To retrieve data from a server without changing it -> Option B

4. Quick Check:

   GET = retrieve data [OK]

Hint: GET always fetches data, never changes it [OK]

Common Mistakes:

• Confusing GET with POST or PUT methods
• Thinking GET can modify data
• Assuming GET deletes data

2. Which of the following is the correct way to add query parameters to a GET request URL in Postman?

easy

A. https://api.example.com/data?user=123&active=true

B. https://api.example.com/data/user=123&active=true

C. https://api.example.com/data#user=123&active=true

D. https://api.example.com/data/user/123/active/true

Solution

1. Step 1: Identify query parameter syntax

   Query parameters start with a question mark (?) and separate key-value pairs with ampersands (&).

2. Step 2: Check each URL format

   https://api.example.com/data?user=123&active=true uses ? and & correctly; others use incorrect separators or path segments.

3. Final Answer:

   https://api.example.com/data?user=123&active=true -> Option A

4. Quick Check:

   Query params start with ? and use & [OK]

Hint: Use ? for first param, & for others in URL [OK]

Common Mistakes:

• Using slashes instead of ? and & for parameters
• Using # which is for fragments, not parameters
• Omitting the question mark before parameters

3. Given this GET request in Postman:

GET https://api.example.com/users?id=5

What is the expected status code if the user with id 5 exists?

medium

A. 404 Not Found

B. 500 Internal Server Error

C. 200 OK

D. 301 Moved Permanently

Solution

1. Step 1: Understand HTTP status codes

   200 OK means the request succeeded and data is returned.

2. Step 2: Match status with scenario

   If user id 5 exists, server returns 200 OK with user data; 404 means not found, 500 is server error, 301 is redirect.

3. Final Answer:

   200 OK -> Option C

4. Quick Check:

   Existing data returns 200 OK [OK]

Hint: 200 means success, 404 means missing data [OK]

Common Mistakes:

• Confusing 404 with 200
• Thinking 500 means data not found
• Assuming 301 is success status

4. You send a GET request in Postman but receive a 400 Bad Request error. What is the most likely cause?

medium

A. The URL has incorrect or malformed query parameters

B. The server is down and not responding

C. The requested resource does not exist

D. The request method should be POST instead of GET

Solution

1. Step 1: Understand 400 Bad Request meaning

   400 means the server could not understand the request due to invalid syntax.

2. Step 2: Analyze causes

   Malformed query parameters cause bad syntax; server down causes no response (timeout), resource missing causes 404, wrong method causes 405.

3. Final Answer:

   The URL has incorrect or malformed query parameters -> Option A

4. Quick Check:

   400 = bad syntax in request [OK]

Hint: 400 means bad request syntax, check URL parameters [OK]

Common Mistakes:

• Confusing 400 with server down errors
• Assuming 400 means resource missing
• Thinking method mismatch causes 400

5. You want to test a GET request in Postman that retrieves a list of products filtered by category and sorted by price ascending. Which URL format correctly applies both filters?

hard

A. https://api.example.com/products?category=electronics&sort=price-desc

B. https://api.example.com/products/category=electronics/sort=price_asc

C. https://api.example.com/products?category=electronics#sort=price_asc

D. https://api.example.com/products?category=electronics&sort=price_asc

Solution

1. Step 1: Use correct query parameter syntax

   Parameters start with ? and separate keys with &. The keys and values must match expected API parameters.

2. Step 2: Check parameter values for sorting

   https://api.example.com/products?category=electronics&sort=price_asc uses 'sort=price_asc' which clearly means ascending price. https://api.example.com/products?category=electronics&sort=price-desc uses 'price-desc' which is descending, not ascending.

3. Final Answer:

   https://api.example.com/products?category=electronics&sort=price_asc -> Option D

4. Quick Check:

   Use ? and & with correct param names and values [OK]

Hint: Use ? then & for multiple filters with correct values [OK]

Common Mistakes:

• Using # instead of & for parameters
• Mixing path segments with query parameters
• Using wrong sort value (desc instead of asc)