Rate Limits

This page will answer your questions on rate limits imposed on agency campaigns. This applies to all agencies.

Key information

1. The default rate limit is 10 TPS per campaign ID.

   -> This is defined as the number of API calls per second and not the number of messages sent per second.

2. This rate limit is shared across all APIs.

   -> For instance, if within your campaign you call the following:

   1. Single send at 6 TPS; and

   2. Retrieve message at 2 TPS; and

   3. Batch send at 4 TPS,

   then, as this adds up to 12 TPS, you will hit the rate limit and will be given a 429 error.

3. If you need a higher TPS, please reach out to us via the contact form here.

   • In the form,

     1. state your use case

     2. state the ideal TPS needed, and reason needing this higher TPS.

     3. If you're asking for greater than 15 TPS, please provide evidence:

        1. You should provide us with internal logs of your actual historical cases on your old systems that you have hit that higher TPS before. Logs from testing on Postman are not considered proof.

        2. For instance, you can send us historical logs of maximum TPS experienced anytime from Jan 2022 onwards.

Things to note

1. The TPS limit applies only to messags entering the Postman system, not messages sent to the end recipients. Message delivery speeds may be slower than the TPS provided during peak periods, which occur from 8:00 am to 6:00 pm daily.

2. We will prioritise messages in the following manner:

   1. OTP messages using Single Send

   2. All other messages using Single Send

   3. All messages using Batch Send

3. Understand the difference between single and batch sending:

   1. If you're using single send, 1 TPS refers to 1 API call and 1 message to be sent out.

   2. If you're using batch send and you have 20 rows in your file, 1 TPS refers to 1 API call and 20 messages to be sent out.

Other important information

The Postman v2 API uses a number of safeguards against bursts of incoming traffic to help maximise its stability. If you send many requests in quick succession, you might see error responses that show up as status code 429.

Note that we do not queue requests which arrive past the rate limit and such requests are dropped. As such, you will need to retry the same request(s) later.