What is TPS (Transactions Per Second)?
TPS (transactions per second) — also called MPS or send rate — is the throughput ceiling of a messaging bind or account: how many SMS submit_sm PDUs the SMSC accepts per second before it returns throttling errors. A2P binds are provisioned at a contracted TPS; exceeding it triggers ESME_RTHROTTLED responses. TPS, not raw volume, determines how fast a campaign or OTP burst clears. See /answers/what-is-throughput-sla, /answers/what-is-cps, and /tools/smpp-error-codes.
Need help wiring this up?
The pages below are the products and integration guides that put this concept on the wire. If you'd rather walk through it live, our engineering team takes calls same-day during MENA working hours.
Talk to our engineering teamWas this answer helpful?
Your vote helps us prioritise which answers to expand with examples, diagrams, and code snippets.
Talk to a real engineer about your build.
We reply within one business day, and production accounts get 24/7 support. Our solutions engineers ship code, not scripts.