# TPG Telecom

> TPG Telecom Limited is Australia's second-largest telecommunications company, an ASX-listed mobile network operator and fixed broadband carrier formed by the 2020 merger of Vodafone Hutchison Australia and TPG Corporation, selling under the Vodafone, TPG, iiNet, Internode, Lebara and felix brands. It publishes no first-party developer portal and no network APIs: its only public, callable developer surface is the Vodafone Business Messaging Hub, a white-labelled Sinch MessageMedia (Sinch Engage) CPaaS platform running on TPG-branded hosts. On CAMARA and GSMA Open Gateway, TPG is a stated non-participant.

Generated by API Evangelist on 2026-07-25 from the TPG Telecom provider repo. Method: generated — no /llms.txt is published on any TPG Telecom host (probes returned 404).

## APIs

- [TPG Telecom Messaging Hub Contacts API](https://contactsapiv1tgp.docs.apiary.io/): CRUD over contacts, lists and custom fields for SMS/MMS campaigns. Base URL https://api.messaging.tpgtelecom.com.au, 18 operations under /api/v1/contacts. HTTP Basic or HMAC-SHA1 authentication.
- [TPG Telecom Messaging Hub REST API](https://support.messaging.tpgtelecom.com.au/hc/en-us/sections/4750925238671-REST-API-Documentation): SMS/MMS send, replies, delivery reports and webhooks on https://api.messaging.tpgtelecom.com.au. Live and credential-gated; no first-party reference is published.

## Specs

- [API Blueprint — Contacts Management API](blueprint/tpg-telecom-contacts-management-api.apib): API Blueprint 1A, harvested verbatim from the Apiary project TPG embeds in its help centre. The only machine-readable description TPG Telecom publishes. No OpenAPI, Swagger, AsyncAPI, GraphQL schema or Protobuf exists anywhere on a TPG host.

## Artifacts

- [Authentication](authentication/tpg-telecom-authentication.yml): Basic (Base64 api_key:api_secret), HMAC-SHA1 signed Authorization, and legacy username/password credentials. No OAuth 2.0, OIDC, CIBA or mTLS.
- [Conventions](conventions/tpg-telecom-conventions.yml): cursor pagination (nextPageToken/prevPageToken/pageSize, default 1000), UUID identifiers, E.164 channel ids, ISO 8601 timestamps. No idempotency contract, no rate-limit response headers.
- [Error catalogue](errors/tpg-telecom-problem-types.yml): 400/401/403/409/500/501/502/503/504 with a uuid/type/title/detail envelope and a 14-value error type enum.
- [Delivery status codes](errors/tpg-telecom-delivery-status-codes.yml): the 30-code message delivery registry (101–414) plus the eight message statuses, captured from the help centre.
- [Data model](data-model/tpg-telecom-data-model.yml): Contact, ContactChannel, List, CustomField and the relationships between them.
- [Webhooks](asyncapi/tpg-telecom-messaging-webhooks.yml): inbound SMS, opt-out, message delivered and message expired events; console-configured, templated JSON payloads, no signing scheme.
- [Lifecycle](lifecycle/tpg-telecom-lifecycle.yml): URI-path v1 versioning, no deprecation policy, no SLA, Atlassian status page with a dedicated REST API component.
- [Rate limits](rate-limits/tpg-telecom-rate-limits.yml): volume sending limits (daily/monthly/system) rather than request throttling; over-limit messages are Discarded with code 301.
- [Plans](plans/tpg-telecom-plans.yml): five Messaging Hub tiers from $50 to $700 per month, all including REST API access; 12-month minimum term, no free tier.
- [Packages](packages/tpg-telecom-packages.yml): no first-party SDKs; the vendor's Sinch MessageMedia libraries are the de facto client.
- [MCP](mcp/tpg-telecom-mcp.yml): no published MCP server; an /mcp route on the API gateway answers 401 to anonymous requests and could not be verified.
- [Conformance](conformance/tpg-telecom-conformance.yml): no CAMARA, no GSMA Open Gateway, no TM Forum certification, no 3GPP NEF/SCEF exposure.
- [Security](security/tpg-telecom-domain-security.yml): TLS/HSTS/DNSSEC/CAA/SPF/DMARC probe results for TPG hosts.
- [Agent skills](skills/_index.yml): packaged operating instructions for the contact, list and custom-field flows.

## Docs

- [Messaging Hub help centre](https://support.messaging.tpgtelecom.com.au/hc/en-us): 96 articles; the Developer Guides and REST API Documentation sections hold the API material.
- [Creating new API credentials](https://support.messaging.tpgtelecom.com.au/hc/en-us/articles/4750274170383-Creating-new-API-credentials): how Basic, HMAC and legacy keys are minted (administrators only, secret shown once).
- [Create & manage webhooks](https://support.messaging.tpgtelecom.com.au/hc/en-us/articles/4693850901263-Create-manage-webhooks)
- [Message status definitions and codes](https://support.messaging.tpgtelecom.com.au/hc/en-us/articles/4663332574223-Message-status-definitions-and-codes)
- [Viewing and updating SMS limits](https://support.messaging.tpgtelecom.com.au/hc/en-us/articles/4693850081935-Viewing-and-updating-SMS-limits)
- [Messaging Hub product page](https://www.vodafone.com.au/business/messaging-hub): plan tiers and pricing.
- [Status page](https://status.messaging.tpgtelecom.com.au): Atlassian Statuspage with Web Portal, REST API, Email to SMS and Inbound System (Webhooks) components.

## Company

- [TPG Telecom](https://www.tpgtelecom.com.au/)
- [Investor relations](https://www.tpgtelecom.com.au/investor-relations)
- [Media releases](https://www.tpgtelecom.com.au/media_release)
- [Privacy](https://www.tpgtelecom.com.au/about-us/privacy)
- [Website terms](https://www.tpgtelecom.com.au/website-terms)
- [security.txt](https://www.tpgtelecom.com.au/.well-known/security.txt): vulnerability@tpgtelecom.com.au

## Notes for agents

- There is no self-serve signup. Messaging Hub accounts are sold through Vodafone Business, and only an account administrator can mint API keys from the console (Settings > API Settings).
- There is no sandbox, no test mode and no magic test numbers. Every call is live and billable — Failed and Rejected messages may still be charged.
- There is no idempotency key. Retrying a create after a timeout will duplicate the resource.
- Delivery outcome is asynchronous: an accepted send does not mean delivery. Consume delivery receipts (webhooks) and read errors/tpg-telecom-delivery-status-codes.yml.
- Consent is sticky: recreating an UNSUBSCRIBED contact as SUBSCRIBED preserves UNSUBSCRIBED.