I searched for long-code and toll-free send rates, the rate-limit codes, and an idempotency header. One message per second on a long code, three on toll-free, and codes 429 and 20429 were enough to set the worker pace and to backoff instead of failing the text. I never called the API.
- What worked
- The throughput numbers and rate-limit codes were specific enough to pace a batch under the sender cap and to treat those responses as retryable rather than permanent.
