TPG Telecom · Rate Limits

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.

The profile also includes 4 backoff/retry policies defined.

Tagged areas include Telecommunications, Australia, Mobile Network Operator, Broadband, and Messaging.

0 Limits
TelecommunicationsAustraliaMobile Network OperatorBroadbandMessagingSMSIoT5GPartner Gated

Policies

Administrator-configured ceiling on messages sent per billing month. Cannot be set above the account's assigned system limit; a higher ceiling requires a system limit increase request from Settings > Numbers > Settings > Messaging, which raises a support ticket for approval.
Administrator-configured daily ceiling; cannot exceed the monthly limit.
The hard limit assigned to the account by TPG Telecom. Not published; only raised through an approved support request. Limits cannot be set to expire or revert automatically.
No request-per-second or per-minute API throughput limit is documented, and the API Blueprint declares no 429 response and no rate-limit headers on any of its 18 operations.

Sources