Why Timestamp generation in Postman? - Purpose & Use Cases

The Big Idea

What if you never had to type the current time again when testing APIs?

The Scenario

Imagine testing an API that requires a current timestamp for each request. You open a clock, note the time, then type it manually into Postman every single time you send a request.

The Problem

This manual method is slow and tiring. You might mistype the time or forget to update it, causing tests to fail or behave unpredictably. It's like writing the date on every letter by hand instead of using a stamp.

The Solution

Using timestamp generation in Postman automates this process. It inserts the exact current time automatically into your requests, so you never have to type it yourself. This saves time and avoids errors.

Before vs After

✗ Before

POST /api/data
Body: { "time": "2024-06-01T12:00:00Z" }

✓ After

POST /api/data
Body: { "time": "{{$timestamp}}" }

What It Enables

It enables fast, accurate, and repeatable API testing with dynamic current timestamps every time you run your tests.

Real Life Example

When testing a payment API, the server needs the exact current time to validate transactions. Timestamp generation ensures your test requests always have the right time, preventing errors and saving debugging time.

Key Takeaways

Manual timestamp entry is slow and error-prone.

Automated timestamp generation saves time and improves accuracy.

Dynamic timestamps make API tests reliable and repeatable.

Practice

1. What does Date.now() return in Postman scripts?

easy

A. The current date as a string in format YYYY-MM-DD

B. The current time zone offset in minutes

C. The current timestamp in milliseconds since January 1, 1970

D. The current time in seconds since midnight

Solution

1. Step 1: Understand Date.now() function

   Date.now() returns the number of milliseconds elapsed since January 1, 1970 00:00:00 UTC.

2. Step 2: Compare options with this definition

   Only The current timestamp in milliseconds since January 1, 1970 correctly describes this behavior as a timestamp in milliseconds.

3. Final Answer:

   The current timestamp in milliseconds since January 1, 1970 -> Option C

4. Quick Check:

   Date.now() = milliseconds timestamp [OK]

Hint: Remember: Date.now() gives milliseconds since 1970 [OK]

Common Mistakes:

• Thinking Date.now() returns a formatted date string
• Confusing milliseconds with seconds
• Assuming it returns time zone info

2. Which of the following is the correct way to save the current timestamp in a Postman environment variable?

easy

A. pm.environment.set('currentTime', Date.now());

B. pm.environment.get('currentTime', Date.now());

C. pm.environment.save('currentTime', Date.now());

D. pm.environment.store('currentTime', Date.now());

Solution

1. Step 1: Identify the correct method to set environment variables

   In Postman scripts, pm.environment.set(key, value) is used to save a variable.

2. Step 2: Check each option's method name

   Only pm.environment.set('currentTime', Date.now()); uses the correct method set with the right syntax.

3. Final Answer:

   pm.environment.set('currentTime', Date.now()); -> Option A

4. Quick Check:

   Use pm.environment.set() to save variables [OK]

Hint: Use pm.environment.set() to save variables [OK]

Common Mistakes:

• Using pm.environment.get() to save variables
• Using non-existent methods like save() or store()
• Forgetting to pass both key and value

3. What will be the output of this Postman test script snippet?

let start = Date.now();
pm.environment.set('startTime', start);
let end = Date.now();
pm.environment.set('endTime', end);
let duration = pm.environment.get('endTime') - pm.environment.get('startTime');
console.log(duration);

medium

A. A negative number due to subtraction order

B. Zero, because start and end are set at the same time

C. Undefined, because variables are not saved correctly

D. A positive number representing milliseconds elapsed between start and end

Solution

1. Step 1: Understand the timestamp capture

   start and end capture timestamps at two different moments, so end ≥ start.

2. Step 2: Calculate duration

   Subtracting start from end gives the elapsed time in milliseconds, which is positive or zero.

3. Final Answer:

   A positive number representing milliseconds elapsed between start and end -> Option D

4. Quick Check:

   duration = end - start ≥ 0 [OK]

Hint: Subtract start from end timestamps for elapsed time [OK]

Common Mistakes:

• Assuming start and end are identical
• Confusing subtraction order causing negative result
• Thinking variables are not saved properly

4. You wrote this Postman script to save a timestamp:

pm.environment.set('timeStamp', Date.now)

Why does this cause an error or unexpected behavior?

medium

A. Date.now is a function and needs parentheses to execute

B. pm.environment.set() cannot save numbers

C. The variable name 'timeStamp' is reserved

D. Date.now returns a string, not a number

Solution

1. Step 1: Check usage of Date.now

   Date.now is a function reference, not the timestamp itself.

2. Step 2: Identify missing parentheses

   To get the current timestamp, you must call the function with (), like Date.now().

3. Final Answer:

   Date.now is a function and needs parentheses to execute -> Option A

4. Quick Check:

   Call Date.now() with () to get timestamp [OK]

Hint: Always add () to call Date.now() function [OK]

Common Mistakes:

• Forgetting parentheses after Date.now
• Thinking pm.environment.set can't save numbers
• Assuming variable names cause errors

5. You want to measure the response time of an API request in Postman using timestamps. Which script correctly captures the start time before the request and calculates the duration after the response?

hard

A. In Tests: pm.environment.set('startTime', Date.now());In Pre-request Script: let duration = Date.now() - pm.environment.get('startTime');

B. In Pre-request Script: pm.environment.set('startTime', Date.now());In Tests: let duration = Date.now() - pm.environment.get('startTime');
pm.test('Response time', () => pm.expect(duration).to.be.below(2000));

C. In Pre-request Script: let duration = Date.now() - pm.environment.get('startTime');In Tests: pm.environment.set('startTime', Date.now());

D. In Tests: let duration = pm.environment.get('startTime') - Date.now();In Pre-request Script: pm.environment.set('startTime', Date.now());

Solution

1. Step 1: Capture start time before request

   The Pre-request Script runs before the API call, so saving startTime there is correct.

2. Step 2: Calculate duration after response

   The Tests script runs after the response, so subtracting startTime from current time gives elapsed time.

3. Final Answer:

   captures the start time before the request and calculates the duration after the response -> Option B

4. Quick Check:

   Pre-request sets start; Tests calculate duration [OK]

Hint: Set start time pre-request; calculate duration in tests [OK]

Common Mistakes:

• Setting start time after request instead of before
• Subtracting timestamps in wrong order
• Calculating duration before request runs