Tpg Telecom Rate Limits
The Messaging Hub governs consumption with volume sending limits rather than request-rate throttling. Each account carries a system limit set by TPG/Sinch, and administrators can set a monthly and a daily sending limit at or below it. Messages that exceed a limit are marked Discarded with delivery status code 301 — there is no HTTP 429, no Retry-After and no X-RateLimit family of response headers anywhere in the published API Blueprint or the help centre. The numeric system limit is account-specific and is not published, so no per-account figure is recorded here.
Tpg Telecom Rate Limits is the machine-readable rate-limit profile for TPG Telecom on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 4 rate-limit definitions.
The profile also includes 4 backoff/retry policies defined.
Tagged areas include Telecommunications, Australia, Mobile Network Operator, Broadband, and Messaging.
Policies
Sources
- https://support.messaging.tpgtelecom.com.au/hc/en-us/articles/4693850081935-Viewing-and-updating-SMS-limits
- https://support.messaging.tpgtelecom.com.au/hc/en-us/articles/4663332574223-Message-status-definitions-and-codes
- blueprint/tpg-telecom-contacts-management-api.apib
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.