API versioning validation in Postman - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to set the API version header correctly in Postman.

Postman

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

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

Av1

Bver1

Capi_v1

Dversion1

Attempts:

3 left

💡 Hint

Common Mistakes

Using non-standard version strings like 'version1' or 'api_v1' which may not be recognized by the API.

The standard way to specify API version in headers is often 'v1'. This sets the 'Accept-Version' header to 'v1'.

2fill in blank

medium

Complete the test script to check if the API version in the response header is correct.

Postman

pm.test('API version is correct', function () { pm.expect(pm.response.headers.get('[1]')).to.eql('v1'); });

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

AVersion

BContent-Type

CAccept-Version

DAPI-Version

Attempts:

3 left

💡 Hint

Common Mistakes

Checking wrong headers like 'Content-Type' or 'Accept-Version' which are not response version headers.

The response header 'API-Version' is commonly used to indicate the version of the API that responded.

3fill in blank

hard

Fix the error in the test script to correctly validate the API version in the response body JSON.

Postman

pm.test('Response has correct API version', () => { pm.expect(pm.response.json().[1]).to.equal('v1'); });

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

Aversion

BapiVersion

Capi_ver

Dversion_api

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect key names like 'version_api' or 'api_ver' that do not exist in the response.

The response JSON key for API version is usually 'apiVersion' following camelCase naming.

4fill in blank

hard

Fill both blanks to create a test that checks the API version in both header and JSON body.

Postman

pm.test('API version consistency', () => { pm.expect(pm.response.headers.get('[1]')).to.eql('v1'); pm.expect(pm.response.json().[2]).to.eql('v1'); });

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

AAPI-Version

BapiVersion

CAccept-Version

Dversion

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing header and JSON key names or using incorrect keys.

The header 'API-Version' and JSON key 'apiVersion' are standard places to check API version consistency.

5fill in blank

hard

Fill all three blanks to write a pre-request script that sets the API version header dynamically and a test that validates it.

Postman

pm.request.headers.upsert({ key: '[1]', value: '[2]' });
pm.test('Check version header', () => { pm.expect(pm.request.headers.get('[3]')).to.eql('v2'); });

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

AAccept-Version

Bv2

CAPI-Version

DVersion

Attempts:

3 left

💡 Hint

Common Mistakes

Using different header keys in setting and checking causing test failures.

The pre-request script sets 'Accept-Version' header to 'v2'. The test checks the same header for 'v2'.

Practice

1. What is the main purpose of API versioning validation in Postman?

easy

A. To test the API authentication method

B. To check if the API URL is reachable

C. To verify the API response time

D. To ensure the API response uses the correct version

Solution

1. Step 1: Understand API versioning validation

   API versioning validation checks if the API response matches the expected version.

2. Step 2: Identify the main goal in Postman

   In Postman, this means verifying the version value in the response body or headers.

3. Final Answer:

   To ensure the API response uses the correct version -> Option D

4. Quick Check:

   API version check = Correct version [OK]

Hint: Focus on version correctness in API response [OK]

Common Mistakes:

• Confusing version check with response time
• Checking URL reachability instead of version
• Testing authentication instead of version

2. Which Postman test script correctly asserts that the API version in the response header is 'v2'?

easy

A. pm.response.headers.get('api-version').to.eql('v2');

B. pm.expect(pm.response.headers.get('api-version')).to.eql('v2');

C. pm.expect(pm.response.body.apiVersion).to.eql('v2');

D. pm.expect(pm.response.headers['api-version']).to.equal('v2');

Solution

1. Step 1: Check correct method to get header value

   Use pm.response.headers.get('header-name') to get header value in Postman.

2. Step 2: Use pm.expect() with .to.eql() for assertion

   pm.expect(...).to.eql('v2') correctly asserts the value equals 'v2'.

3. Final Answer:

   pm.expect(pm.response.headers.get('api-version')).to.eql('v2'); -> Option B

4. Quick Check:

   Use headers.get() + pm.expect() [OK]

Hint: Use headers.get() with pm.expect().to.eql() for header checks [OK]

Common Mistakes:

• Using pm.response.headers['api-version'] which is undefined
• Calling to.eql() directly on header getter without pm.expect()
• Checking version in body when question asks for header

3. Given this Postman test script, what will be the test result if the response JSON is {"version": "1.0"}?

pm.test('Check API version', () => {
  pm.expect(pm.response.json().version).to.equal('2.0');
});

medium

A. Test throws syntax error

B. Test passes because version key exists

C. Test fails because version is '1.0', not '2.0'

D. Test passes because .to.equal() ignores value

Solution

1. Step 1: Understand the test assertion

   The test expects the version value to be exactly '2.0'.

2. Step 2: Compare actual response version with expected

   The response has version '1.0', which does not equal '2.0', so assertion fails.

3. Final Answer:

   Test fails because version is '1.0', not '2.0' -> Option C

4. Quick Check:

   Expected '2.0' vs actual '1.0' = Fail [OK]

Hint: Match expected version exactly to pass test [OK]

Common Mistakes:

• Assuming test passes if key exists
• Thinking .to.equal() ignores value differences
• Confusing syntax error with assertion failure

4. You wrote this Postman test to check API version in response header:

pm.test('API version is v1', () => {
  pm.expect(pm.response.headers['api-version']).to.eql('v1');
});

But the test always fails. What is the likely issue?

medium

A. pm.response.headers is not an object with keys, use .get() method instead

B. The header name should be capitalized as 'Api-Version'

C. The assertion method should be .to.equal() not .to.eql()

D. pm.expect() cannot be used for header validation

Solution

1. Step 1: Understand how to access headers in Postman

   pm.response.headers is a special object; headers must be accessed with .get('header-name').

2. Step 2: Identify the error in header access

   Using pm.response.headers['api-version'] returns undefined, causing assertion failure.

3. Final Answer:

   pm.response.headers is not an object with keys, use .get() method instead -> Option A

4. Quick Check:

   Use headers.get() to access headers [OK]

Hint: Use headers.get('name') to access headers in Postman [OK]

Common Mistakes:

• Accessing headers like a normal object
• Changing header name case unnecessarily
• Confusing .to.eql() with .to.equal() causing failure

5. You want to validate that your API supports multiple versions: 'v1', 'v2', or 'v3'. Which Postman test script correctly checks the response header 'api-version' against these allowed versions?

hard

A. pm.test('API version is valid', () => {
const version = pm.response.headers.get('api-version');
pm.expect(version).to.be.oneOf(['v1', 'v2', 'v3']);
});

B. pm.test('API version is valid', () => {
const version = pm.response.headers.get('api-version');
pm.expect(version === 'v1' || 'v2' || 'v3').to.be.true;
});

C. pm.test('API version is valid', () => {
const version = pm.response.headers.get('api-version');
pm.expect(version).to.include(['v1', 'v2', 'v3']);
});

D. pm.test('API version is valid', () => {
const version = pm.response.headers.get('api-version');
pm.expect(version).to.eql('v1' || 'v2' || 'v3');
});

Solution

1. Step 1: Understand how to check multiple allowed values

   pm.expect(...).to.be.oneOf(array) checks if value is in the array.

2. Step 2: Analyze each option's correctness

   pm.test('API version is valid', () => { const version = pm.response.headers.get('api-version'); pm.expect(version).to.be.oneOf(['v1', 'v2', 'v3']); }); uses .to.be.oneOf(['v1','v2','v3']) correctly. pm.test('API version is valid', () => { const version = pm.response.headers.get('api-version'); pm.expect(version).to.include(['v1', 'v2', 'v3']); }); uses .to.include(array) which is invalid. pm.test('API version is valid', () => { const version = pm.response.headers.get('api-version'); pm.expect(version === 'v1' || 'v2' || 'v3').to.be.true; }); uses incorrect boolean logic. pm.test('API version is valid', () => { const version = pm.response.headers.get('api-version'); pm.expect(version).to.eql('v1' || 'v2' || 'v3'); }); uses .to.eql() with || which evaluates incorrectly.

3. Final Answer:

   pm.expect(version).to.be.oneOf(['v1', 'v2', 'v3']); -> Option A

4. Quick Check:

   Use .to.be.oneOf() for multiple allowed values [OK]

Hint: Use .to.be.oneOf() to check multiple valid versions [OK]

Common Mistakes:

• Using .to.include() incorrectly on array
• Writing boolean OR logic inside pm.expect()
• Using .to.eql() with OR operator causing wrong check