Rate limit testing in Postman - Build an Automation Script

Verify API rate limiting works as expected

Preconditions (2)

Step 1: Send 10 requests to the API endpoint within 1 minute

Step 2: Observe the response status codes and messages for each request

✅ Expected Result: The first N requests (within the allowed limit) return status 200 OK. Requests exceeding the rate limit return status 429 Too Many Requests with an appropriate error message.

Automation Requirements - Postman

Assertions Needed:

Verify response status code is 200 for allowed requests

Verify response status code is 429 for requests exceeding the limit

Verify error message is present in 429 responses

Best Practices:

Use Postman Collection Runner to send multiple requests

Use environment variables to track request count

Add tests in Postman scripts to assert status codes and messages

Add delays if needed to simulate timing between requests

Automated Solution

Postman

/* Postman Pre-request Script */
if (!pm.environment.get('requestCount')) {
    pm.environment.set('requestCount', 1);
} else {
    let count = parseInt(pm.environment.get('requestCount'));
    pm.environment.set('requestCount', count + 1);
}

/* Postman Test Script */
const count = parseInt(pm.environment.get('requestCount'));

if (count <= 10) {
    pm.test('Status code is 200 for allowed requests', function () {
        pm.response.to.have.status(200);
    });
} else {
    pm.test('Status code is 429 for rate limit exceeded', function () {
        pm.response.to.have.status(429);
    });
    pm.test('Response has rate limit error message', function () {
        pm.expect(pm.response.text()).to.include('rate limit');
    });
}

The Pre-request Script initializes and increments a counter stored in Postman environment variables to track how many requests have been sent.

The Test Script checks the current count. For the first 10 requests, it asserts the response status is 200 OK. For requests beyond 10, it asserts the status is 429 Too Many Requests and verifies the response contains a rate limit error message.

This approach simulates sending multiple requests and validates the API's rate limiting behavior automatically within Postman.

Common Mistakes - 3 Pitfalls

{'mistake': 'Not resetting the request count between test runs', 'why_bad': 'The counter keeps increasing across runs, causing false failures or passes.', 'correct_approach': "Reset the environment variable 'requestCount' to 0 or remove it before starting a new test run."}

Not checking for the correct status code for rate limit exceeded

{'mistake': 'Sending all requests too quickly without delay', 'why_bad': 'Some APIs count requests per time window; sending too fast may not simulate real usage.', 'correct_approach': "Add delays between requests if needed using Postman Collection Runner's delay option."}

Bonus Challenge

Now add data-driven testing with 3 different API endpoints to verify rate limiting on each.

Show Hint

Practice

1. What is the main purpose of rate limit testing in Postman?

easy

A. To validate user input forms

B. To verify the UI layout of the application

C. To test database connection speed

D. To check if the system blocks too many requests in a short time

Solution

1. Step 1: Understand rate limit testing goal

   Rate limit testing checks if the system prevents too many requests sent quickly.

2. Step 2: Match purpose with options

   Only To check if the system blocks too many requests in a short time describes blocking too many requests, which is the goal of rate limit testing.

3. Final Answer:

   To check if the system blocks too many requests in a short time -> Option D

4. Quick Check:

   Rate limit testing = block too many requests [OK]

Hint: Rate limit testing checks request blocking speed [OK]

Common Mistakes:

• Confusing rate limit testing with UI or database testing
• Thinking it tests input validation
• Ignoring the request frequency aspect

2. Which Postman feature helps simulate multiple rapid requests for rate limit testing?

easy

A. Collection Runner

B. Monitor Scheduler

C. Environment Variables

D. Pre-request Script Editor

Solution

1. Step 1: Identify features for sending multiple requests

   Collection Runner allows running a set of requests repeatedly and quickly.

2. Step 2: Compare with other options

   Monitor Scheduler runs tests on schedule, Environment Variables store data, Pre-request Script Editor runs scripts before requests. Only Collection Runner sends many requests fast.

3. Final Answer:

   Collection Runner -> Option A

4. Quick Check:

   Multiple rapid requests = Collection Runner [OK]

Hint: Use Collection Runner to send many requests fast [OK]

Common Mistakes:

• Choosing Monitor Scheduler which runs slower
• Confusing environment variables with request sending
• Thinking pre-request scripts send requests

3. In Postman, you send 10 requests quickly to an API with a rate limit of 5 requests per minute. What status code do you expect for the 6th request?

medium

A. 200 OK

B. 429 Too Many Requests

C. 404 Not Found

D. 500 Internal Server Error

Solution

1. Step 1: Understand API rate limit behavior

   The API allows only 5 requests per minute; requests beyond that get blocked.

2. Step 2: Identify expected status code for blocked requests

   HTTP status 429 means "Too Many Requests", used when rate limit is exceeded.

3. Final Answer:

   429 Too Many Requests -> Option B

4. Quick Check:

   Exceeded requests = 429 status [OK]

Hint: 429 means rate limit exceeded [OK]

Common Mistakes:

• Expecting 200 OK for all requests
• Confusing 404 with rate limit errors
• Thinking server error 500 means rate limit

4. You wrote a Postman test script to check for status 429 after rapid requests but it always passes even when the server returns 200. What is the likely error?

medium

A. Checking 'pm.response.code' but comparing with string '429' instead of number 429

B. Using 'pm.response.status' but comparing with number 429 instead of string '429 Too Many Requests'

C. Not sending enough requests to exceed the rate limit

D. Using 'pm.response.code' instead of 'pm.response.status'

Solution

1. Step 1: Understand Postman response code type

   pm.response.code returns a number, so comparisons must be with numbers, not strings.

2. Step 2: Identify comparison mistake

   Comparing pm.response.code (number) with string '429' always fails, so test passes incorrectly.

3. Final Answer:

   Checking 'pm.response.code' but comparing with string '429' instead of number 429 -> Option A

4. Quick Check:

   Compare status code as number, not string [OK]

Hint: Compare status codes as numbers, not strings [OK]

Common Mistakes:

• Comparing number with string in assertions
• Not sending enough requests to trigger rate limit
• Confusing pm.response.code and pm.response.status

5. You want to test an API's rate limit of 10 requests per minute using Postman. Which approach best ensures you detect the limit accurately?

hard

A. Send 10 requests slowly over 2 minutes and check for status 429

B. Send 5 requests spaced 10 seconds apart and check for status 200

C. Send 20 requests rapidly using Collection Runner and check for status 429 after 10th request

D. Send 1 request and check if status is 429

Solution

1. Step 1: Understand rate limit testing requirements

   To detect rate limit, send more requests than allowed quickly to trigger limit.

2. Step 2: Evaluate options for detecting limit

   Send 20 requests rapidly using Collection Runner and check for status 429 after 10th request sends 20 rapid requests exceeding 10 limit, so status 429 should appear after 10th request. Others send fewer or slower requests, unlikely to trigger limit.

3. Final Answer:

   Send 20 requests rapidly using Collection Runner and check for status 429 after 10th request -> Option C

4. Quick Check:

   Exceed limit quickly to detect 429 [OK]

Hint: Send more than limit requests fast to catch 429 [OK]

Common Mistakes:

• Sending requests too slowly to trigger limit
• Sending fewer requests than limit
• Checking wrong status codes