Everything worth knowing, nothing that isn't.
Use SMPP for sustained volume
REST has no fixed per-account rate limit at BroadNet; SMPP 3.4 binds suit sustained volumes of several hundred messages per second or more (up to 30,000 SMS/s per node), which is why OTP services and large senders use them. See /compare/sms-api-vs-smpp and /answers/what-is-smpp.
Provision capacity ahead of peaks
Operator throughput is allocated, so reserve headroom before a known spike rather than hitting the ceiling during it. Plan for the burst, not the average. See /answers/what-is-tps and /answers/what-is-throughput-sla.
Distribute and back off
Spread load across multiple binds or routes, and handle throttling responses with exponential backoff so you ride the limit smoothly instead of failing. See /answers/what-is-rate-limiting-sms and /answers/what-is-route-failover.
Do not waste capacity
Validate numbers with HLR lookups and keep messages to one segment, so your throughput goes to deliverable messages rather than dead numbers or extra segments. See /products/hlr-lookup and /answers/sms-character-limit-explained.