TPG Telecom Limited is Australia's second-largest telecommunications company and an ASX-listed mobile network operator and fixed broadband carrier, formed by the 2020 merger of Vodafone Hutchison Australia and TPG Corporation. It runs its own mobile network reaching 98.4% of the Australian population and sells under the Vodafone, TPG, iiNet, Internode, Lebara and felix brands, with business, enterprise, government and wholesale services consolidated under Vodafone Business. In the telecom API value chain TPG Telecom sits squarely on the network side and not the developer side: it publishes no first-party developer portal, no downloadable OpenAPI, 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 at messaging.tpgtelecom.com.au and api.messaging.tpgtelecom.com.au, with documentation served from a Zendesk help centre and an Apiary API Blueprint owned by MessageMedia. On the sector's defining signal, CAMARA and GSMA Open Gateway, TPG Telecom is a stated non-participant: while Telstra went live with Number Verification and SIM Swap through Aduna and Optus signalled it would follow, TPG's public position is that it is "closely watching developments like GSMA Open Gateway" while prioritising local scam prevention — a watching brief, not an implementation. TPG Telecom is therefore partner-gated and aggregator-mediated: developers reach its network through a CPaaS supplier, not through TPG.
TPG Telecom is listed with 2 APIs on the APIs.io network. Tagged areas include Telecommunications, Australia, Mobile Network Operator, Broadband, and Messaging.
The TPG Telecom catalog on APIs.io includes 1 event-driven AsyncAPI specification.
TPG Telecom’s developer surface includes authentication, documentation, getting-started guide, support, pricing, legal docs, and 33 more developer resources.
Regulatory Posture applies to this provider. Its tags matched the
Telecommunications regime, so
Regulatory Posture carries 15 points of the composite.
If this regime is wrong for your business, say so on your
provider repo — the
applicability map is public and we will correct it.
Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for
this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero:
never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and
several others — scorable at all.
The six quality facets above are damped to 85 points between them,
because the conditional facet above carries the other
15. That is why each facet's contribution is shown against a damped
maximum: raising a quality facet moves the composite by 85% of its nominal
weight, not 100%. The full arithmetic is at apis.io/rating/.
Show this score on your site.
It updates itself when the score changes. Paste this where you link to your API docs:
<a href="https://apis.io/providers/tpg-telecom/"><img src="https://apis.io/badge/tpg-telecom/card.svg" alt="TPG Telecom on APIs.io — Kin Score by API Evangelist"></a>
Other styles, a README pill and a shields.io endpoint are on the badge page.
Raise your score.
Agent readiness — checks not met, largest first (exact, from this profile):
MCP Server+12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Idempotency+9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
A2A Agent Card+8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Request/Response Examples+7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link
The Kin Score Market layer reads a provider inside its market:
its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted:
not part of the Kin Score or agent readiness.
Registered MCP server and declares compatibility are report only — not weighted.
Undeclared means we found nothing we can read, so there is no number: we never infer integrations.
Contacts Management API for the Vodafone Business Messaging Hub, providing CRUD over contacts, lists and custom fields for SMS/MMS campaigns. Documented as an Apiary API Bluepri...
The SMS/MMS REST API of the Vodafone Business Messaging Hub, listed on the product page as "Access to our REST API" on every plan tier. The API is live on the TPG-branded host h...
aid: tpg-telecom
url: https://raw.githubusercontent.com/api-evangelist/tpg-telecom/refs/heads/main/apis.yml
name: TPG Telecom
kind: company
description: 'TPG Telecom Limited is Australia''s second-largest telecommunications company and an ASX-listed mobile network
operator and fixed broadband carrier, formed by the 2020 merger of Vodafone Hutchison Australia and TPG Corporation. It
runs its own mobile network reaching 98.4% of the Australian population and sells under the Vodafone, TPG, iiNet, Internode,
Lebara and felix brands, with business, enterprise, government and wholesale services consolidated under Vodafone Business.
In the telecom API value chain TPG Telecom sits squarely on the network side and not the developer side: it publishes no
first-party developer portal, no downloadable OpenAPI, 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 at messaging.tpgtelecom.com.au and api.messaging.tpgtelecom.com.au, with documentation served from a Zendesk help
centre and an Apiary API Blueprint owned by MessageMedia. On the sector''s defining signal, CAMARA and GSMA Open Gateway,
TPG Telecom is a stated non-participant: while Telstra went live with Number Verification and SIM Swap through Aduna and
Optus signalled it would follow, TPG''s public position is that it is "closely watching developments like GSMA Open Gateway"
while prioritising local scam prevention — a watching brief, not an implementation. TPG Telecom is therefore partner-gated
and aggregator-mediated: developers reach its network through a CPaaS supplier, not through TPG.'
deliveryModel:
model: saas
open_source: false
commercial: true
callable_host: false
label: Hosted service · you call their endpoint
confidence: medium
source:
- pricing
generated: '2026-08-28'
method: derived
accessModel:
pricing: paid
onboarding: unknown
trial: false
try_now: false
public: false
gated: partner
gated_source:
- tag:Partner Gated
label: Paid
confidence: high
probe_state: covered
source:
- plans
- authentication
- rate-limits
- security
generated: '2026-11-06'
method: derived
image: https://www.tpgtelecom.com.au/themes/custom/tpg/TPG_Telecom_Logo_RGB.png
tags:
- Telecommunications
- Australia
- Mobile Network Operator
- Broadband
- Messaging
- SMS
- IoT
- 5G
created: '2026-07-25'
modified: '2026-10-20'
specificationVersion: '0.23'
maintainers:
- FN: Kin Lane
email: kin@apievangelist.com
common:
- type: Deprecation
url: lifecycle/tpg-telecom-lifecycle.yml
- type: Hosts
url: hosts/tpg-telecom-hosts.yml
- type: IntegrationEdges
url: integrations/tpg-telecom-integration-edges.yml
- type: Vendors
url: vendors/tpg-telecom-vendors.yml
- type: VulnerabilityDisclosure
url: security/tpg-telecom-vulnerability-disclosure.yml
- type: DomainSecurity
url: security/tpg-telecom-domain-security.yml
- type: Security
url: https://www.tpgtelecom.com.au/.well-known/security.txt
- type: SecurityTxt
url: well-known/tpg-telecom-security.txt
- type: WellKnown
url: well-known/tpg-telecom-well-known.yml
- type: Authentication
url: authentication/tpg-telecom-authentication.yml
- type: Conventions
url: conventions/tpg-telecom-conventions.yml
- type: ErrorCatalog
url: errors/tpg-telecom-problem-types.yml
- type: ErrorCodes
url: errors/tpg-telecom-delivery-status-codes.yml
- type: DataModel
url: data-model/tpg-telecom-data-model.yml
- type: Lifecycle
url: lifecycle/tpg-telecom-lifecycle.yml
- type: StatusPage
url: https://status.messaging.tpgtelecom.com.au
- type: Webhooks
url: asyncapi/tpg-telecom-messaging-webhooks.yml
- type: X-MCPServerCandidate
url: mcp/tpg-telecom-mcp.yml
note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: Conformance
url: conformance/tpg-telecom-conformance.yml
- type: AgentSkill
url: skills/_index.yml
- type: Plans
url: plans/tpg-telecom-plans.yml
- type: RateLimits
url: rate-limits/tpg-telecom-rate-limits.yml
- type: Website
url: https://www.tpgtelecom.com.au/
- type: About
url: https://www.tpgtelecom.com.au/about-us
- type: Contact
url: https://www.tpgtelecom.com.au/contact
- type: Documentation
url: https://support.messaging.tpgtelecom.com.au/hc/en-us
- type: GettingStarted
url: https://support.messaging.tpgtelecom.com.au/hc/en-us/sections/4656402628367-Quick-Start-Guides
- type: Support
url: https://support.messaging.tpgtelecom.com.au/hc/en-us/articles/4783185128847-Contacting-us
- type: Pricing
url: https://www.vodafone.com.au/business/messaging-hub
- type: Login
url: https://messaging.tpgtelecom.com.au/login
- type: TermsOfService
url: https://www.tpgtelecom.com.au/website-terms
- type: PrivacyPolicy
url: https://www.tpgtelecom.com.au/about-us/privacy
- type: Legal
url: https://www.tpgtelecom.com.au/legal
- type: Press
url: https://www.tpgtelecom.com.au/media_release
- type: Careers
url: https://www.tpgtelecom.com.au/careers
- type: GitHubOrganization
url: https://github.com/tpgtelecom
- type: LinkedIn
url: https://www.linkedin.com/company/tpg-telecom/
- type: InvestorRelations
url: https://www.tpgtelecom.com.au/investor-relations
- type: Review
url: review.yml
apis:
- aid: tpg-telecom:tpg-telecom-messaging-hub-contacts-api
name: TPG Telecom Messaging Hub Contacts API
description: Contacts Management API for the Vodafone Business Messaging Hub, providing CRUD over contacts, lists and custom
fields for SMS/MMS campaigns. Documented as an Apiary API Blueprint (project subdomain contactsapiv1tgp, owner "MessageMedia")
embedded in the TPG Telecom Messaging Hub help centre. The blueprint declares the base URI https://api.messaging.tpgtelecom.com.au
and 18 operations across /api/v1/contacts/contacts, /api/v1/contacts/lists and /api/v1/contacts/custom-fields. Authentication
is HTTP Basic (Base64 api_key:api_secret) or an hmac-sha1 signed Authorization header. No OpenAPI or Swagger document
is published — the Apiary project's description format is apiblueprint, and its swagger.json endpoint returns project
metadata only.
humanURL: https://contactsapiv1tgp.docs.apiary.io/
baseURL: https://api.messaging.tpgtelecom.com.au
tags:
- Contacts
- Messaging
- CPaaS
properties:
- type: APIBlueprint
url: blueprint/tpg-telecom-contacts-management-api.apib
- type: APIReference
url: https://contactsapiv1tgp.docs.apiary.io/
- type: Documentation
url: https://support.messaging.tpgtelecom.com.au/hc/en-us/articles/11469281100559-Contacts-API
- type: Documentation
url: https://support.messaging.tpgtelecom.com.au/hc/en-us/sections/4750925238671-REST-API-Documentation
- type: Authentication
url: https://support.messaging.tpgtelecom.com.au/hc/en-us/articles/4750274170383-Creating-new-API-credentials
- aid: tpg-telecom:tpg-telecom-messaging-hub-rest-api
name: TPG Telecom Messaging Hub REST API
description: The SMS/MMS REST API of the Vodafone Business Messaging Hub, listed on the product page as "Access to our REST
API" on every plan tier. The API is live on the TPG-branded host https://api.messaging.tpgtelecom.com.au — anonymous probes
on 2026-07-25 returned HTTP 401 Unauthorized (route present, credentials required) for /v1/messages, /v1/replies, /v1/delivery_reports
and /v1/webhooks, while unrouted paths returned 404. Credentials are issued from the Messaging Hub console as REST Basic,
REST HMAC, or legacy username/password keys. The full reference is not published as a first-party developer portal; the
platform is a white-labelled Sinch MessageMedia deployment and the help centre's "API Documentation" article is served
behind a Cloudflare bot challenge. No OpenAPI, Swagger, AsyncAPI, Postman collection, GraphQL surface, or first-party
SDK was found.
humanURL: https://support.messaging.tpgtelecom.com.au/hc/en-us/sections/4750925238671-REST-API-Documentation
baseURL: https://api.messaging.tpgtelecom.com.au
tags:
- Messaging
- SMS
- MMS
- Webhook
- CPaaS
tags_raw:
- Messaging
- SMS
- MMS
- Webhooks
- CPaaS
properties:
- type: Documentation
url: https://support.messaging.tpgtelecom.com.au/hc/en-us/sections/4750925238671-REST-API-Documentation
- type: Documentation
url: https://www.vodafone.com.au/business/messaging-hub
- type: APIReference
url: https://support.messaging.tpgtelecom.com.au/hc/en-us/articles/4750142926479-API-Documentation
- type: Webhooks
url: https://support.messaging.tpgtelecom.com.au/hc/en-us/articles/4693850901263-Create-manage-webhooks
- type: Authentication
url: https://support.messaging.tpgtelecom.com.au/hc/en-us/articles/4750274170383-Creating-new-API-credentials
- type: SignUp
url: https://messaging.tpgtelecom.com.au/login
x-coverage:
state: covered
reason: enriched
detail: 'Identity pass 2026-10-20: Website www.tpgtelecom.com.au verified 200 (title "TPG Telecom"); logo taken from the
site header. support.messaging.tpgtelecom.com.au pointers answer 403 with a Cloudflare "Just a moment..." challenge (live
page behind edge policy, kept). messaging.tpgtelecom.com.au/login not fetched (auth endpoint, probe-safety rule 3).'
evidence:
- url: https://www.tpgtelecom.com.au/
status: 200
- url: https://www.tpgtelecom.com.au/themes/custom/tpg/TPG_Telecom_Logo_RGB.png
status: 200
- url: https://www.tpgtelecom.com.au/contact
status: 200
- url: https://support.messaging.tpgtelecom.com.au/hc/en-us
status: 403
- url: https://status.messaging.tpgtelecom.com.au
status: 200
- url: https://contactsapiv1tgp.docs.apiary.io/
status: 200
x-tags-removed:
- Partner Gated
x-enrichment:
date: '2026-10-20'
status: enriched
artifacts_added: 3
pass: modular-v1
engine: identity=anthropic,contract=anthropic,surfaces=anthropic,docs=anthropic,regulatory=anthropic
TPG Telecom API — frequently asked questions
Does TPG Telecom have an API?
Yes. APIs.io lists 2 APIs from TPG Telecom, including TPG Telecom Messaging Hub Contacts API and TPG Telecom Messaging Hub REST API.
How do I authenticate with the TPG Telecom API?
TPG Telecom uses bearer-token authentication (http/hmac · 3 schemes). The details are profiled on APIs.io as Tpg Telecom Authentication.
How much does the TPG Telecom API cost?
TPG Telecom publishes its prices; its Messaging Hub $50 plan is $50 as of 2026-10-20. APIs.io lists 5 pricing plans for TPG Telecom, with each plan's price, limits and inclusions under Pricing on this page.
Is the TPG Telecom API ready for AI agents?
TPG Telecom has a Kin Score of 51.4 out of 100 (developing) and an Agent Readiness score of 26.1 (agent-aware), scored by API Evangelist on 2026-11-06.
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.
Kin Score
How this is scored →
It updates itself when the score changes. Paste this where you link to your API docs: