This is not our API. This repository is an independent, third-party profile of a company's publicly available API surface, maintained by API Evangelist. API Evangelist does not operate, host, resell, or support this company's APIs, and is not affiliated with or endorsed by the company unless stated on the profile.
Where the information came from. Everything here is assembled from material a member of the public can reach with a browser and no credentials — the company's own website, developer portal and documentation, the specifications it publishes for public use (OpenAPI, AsyncAPI, JSON Schema,
apis.json,llms.txtand similar), its public repositories, and its public status, pricing and changelog pages. Nothing here is obtained by breaching a system, defeating an access control, or using credentials of any kind.The rating is an independent assessment. The Kin Score and Agent Readiness rating are independently calculated scores of a company's public API artifacts, produced by API Evangelist against a published rubric. They are not certifications, endorsements, security assessments, or audits, and they score published artifacts — not the quality, safety, or security of the software.
Corrections, re-scores, and removal are free. No partnership, contract, or purchase is required, and you do not need to justify the request.
- Something wrong? Open an issue on this repository, or email info@apievangelist.com.
- Published something new? Ask for a re-score and we will re-run the rating.
- Want the listing taken down? Say so and we will honor it. The profile is reduced to your company name, a factual description, and a link to your own site, and the company is recorded as unrated — never scored zero for having asked.
Response times. Acknowledgement within one business day; removal or restriction within two business days; corrections and re-scores within five business days.
On a security or compliance team? Email info@apievangelist.com with security in the subject line and you will get a person, not a form. We will tell you exactly which public URLs this profile was built from so your team can see the same surface we did, and we will take the listing down on request while you work through it.
Full detail: Where this data comes from
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.
APIs.json: https://raw.githubusercontent.com/api-evangelist/tpg-telecom/refs/heads/main/apis.yml
- Telecommunications
- Australia
- Mobile Network Operator
- Broadband
- Messaging
- SMS
- IoT
- 5G
- Partner Gated
- Created: 2026-07-25
- Modified: 2026-07-25
TPG Telecom publishes no first-party developer portal and no OpenAPI. Every probed developer hostname either fails to resolve (developer.tpgtelecom.com.au, developers.tpgtelecom.com.au, docs.tpgtelecom.com.au, opengateway.tpgtelecom.com.au, developer.vodafone.com.au) or returns 404 (/developer, /api, /opengateway on the corporate site; api.tpgtelecom.com.au root).
The one public, callable developer surface is the Vodafone Business Messaging Hub — and it is not TPG's own software. messaging.tpgtelecom.com.au returns HTTP 200 with the page title "Login to Sinch Engage | Messaging Platform for Growing Businesses": a white-labelled Sinch MessageMedia CPaaS console on a TPG-branded host. The API host api.messaging.tpgtelecom.com.au is live, returning 401 on /v1/messages, /v1/replies, /v1/delivery_reports, /v1/webhooks and /api/v1/contacts/contacts. Documentation lives in a Zendesk help centre, and the Contacts API reference is an Apiary API Blueprint whose project owner field reads "MessageMedia". TPG's own credential article closes by telling the reader to "connect with your Sinch MessageMedia account."
Non-participant. No CAMARA API is exposed, no Open Gateway portal exists, and TPG is not on the operator side of Aduna. In Australia, Telstra went live first with Number Verification and SIM Swap delivered to Aduna Global, and Optus signalled it would follow. TPG Telecom's public position, from its senior customer security, fraud and scam governance manager, is that it is "closely watching developments like GSMA Open Gateway, but our priority right now is delivering practical, locally-focused scam prevention measures." That is a watching brief — not an implementation, and not even a press release to discount.
No TM Forum Open API conformance certification was found. No NEF/SCEF, network-slicing or edge/MEC API is published. The Managed IoT Connectivity page mentions "a catalogue of API's" without naming, linking or documenting one. TPG runs Google Cloud Apigee internally — an API programme with no public face.
Contacts, lists and custom fields for the Vodafone Business Messaging Hub — 18 operations across /api/v1/contacts/contacts, /api/v1/contacts/lists and /api/v1/contacts/custom-fields.
- Human URL: https://contactsapiv1tgp.docs.apiary.io/
- Base URL:
https://api.messaging.tpgtelecom.com.au
- API Blueprint — harvested verbatim, API Blueprint 1A (not OpenAPI)
- API Reference
- Documentation
- Authentication
The SMS/MMS REST API of the Messaging Hub, sold as "Access to our REST API" on every plan tier. Live but undocumented in public spec form.
- Human URL: https://support.messaging.tpgtelecom.com.au/hc/en-us/sections/4750925238671-REST-API-Documentation
- Base URL:
https://api.messaging.tpgtelecom.com.au
HTTP Basic (Base64(api_key:api_secret)), HMAC (algorithm="hmac-sha1"), and a legacy username/password scheme. Keys are minted inside the console by account administrators only — there is no public self-serve developer signup. No OAuth2, no OIDC, and no CIBA (both /.well-known/openid-configuration and /.well-known/oauth-authorization-server return 404).
Console-configured outbound callbacks with a templated JSON body. Events: SMS received, opt-out occurred, message delivered, message expired. No AsyncAPI is published.
- Website
- About
- Messaging Hub support
- Vulnerability disclosure
- GitHub (0 public repositories)
- Investor relations
See review.yml for the full reviewer findings, probe log with HTTP statuses, and provenance for the harvested API Blueprint.