# Three UK > Three UK (Hutchison 3G UK Limited, Reading, England) is a UK mobile network operator — 5G mobile, home and mobile broadband, and the SMARTY MVNO sub-brand — and since 31 May 2025 a wholly owned subsidiary of VodafoneThree (Vodafone Group 51% / CK Hutchison Holdings 49%). It is a network owner and access provider, not a developer platform. Three UK publishes **no public API**: no developer portal, no self-serve signup, no OpenAPI/AsyncAPI/GraphQL/gRPC contract, no SDKs, no sandbox, and no public Postman workspace. It is nonetheless a named CAMARA Project participant and a GSMA Open Gateway member through CK Hutchison Group Telecom, and its CAMARA SIM Swap, KYC Age Verification and KYC Tenure APIs are commercially launched — reachable only through channel partners and aggregators, never from a Three UK surface. Generated by API Evangelist from the api-evangelist/three-uk catalog entry. Provenance: generated (no provider-published llms.txt exists — https://www.three.co.uk/llms.txt returns 404). ## APIs - **None.** Three UK lists no APIs. `apis[]` in its APIs.json is intentionally empty. Listing its CAMARA network APIs would misrepresent third-party press coverage and aggregator catalogues as first-party Three UK documentation. ## Network APIs (implemented by Three, published by others) - [CAMARA Project](https://camaraproject.org/): the specifications Three UK's network APIs conform to, published by CAMARA — not by Three UK. - [CAMARA governance participants](https://github.com/camaraproject/Governance/blob/main/PARTICIPANTS.MD): lists "Three UK | Jason Tesh", plus four further participants under "Hutchison". - [GSMA Open Gateway](https://www.gsma.com/solutions-and-impact/gsma-open-gateway/): the programme Three participates in via CK Hutchison Group Telecom. - [UK operator launch announcement, 23 September 2025](https://www.gsma.com/newsroom/press-release/uk-mobile-operators-launch-age-verification-and-anti-fraud-apis-through-gsma-open-gateway-initiative/): BT/EE, CK Hutchison Group Telecom (Three), Virgin Media O2 and Vodafone Group commercially launch KYC Age Verification and KYC Tenure; SIM Swap already available; KYC Match committed. - How to actually reach them: through aggregators and channel partners. GSMA names **JT Group (Jersey Telecom)** and **TMT.ID** as already processing UK operator network API traffic. Three UK's majority owner Vodafone Group is a founding venture partner in **Aduna**; Three UK itself is not an Aduna partner. ## Company - [Three UK](https://www.three.co.uk/): consumer site. - [Three Business](https://www.three.co.uk/business): business connectivity. - [Three Group Solutions](https://groupsolutions.three.com/): CK Hutchison group B2B — Enterprise, IoT, Private Networks, Wholesale, MVNO. Marketed commercially; exposes no API surface. - [CKH Innovations Opportunities Development](https://ckhiod.com/): the group innovation hub. - [SMARTY](https://smarty.co.uk/): Three UK's own MVNO sub-brand. Also publishes no API. - [Blog](https://www.three.co.uk/blog) - [Support](https://www.three.co.uk/support) - [My3 account (login)](https://www.three.co.uk/account) ## Operations - [Network status — affected areas](https://www.three.co.uk/support/network-and-coverage/affected-areas): the live service-status surface. - [Coverage and network status checker](https://www.three.co.uk/support/network-and-coverage/coverage) - [3G switch-off](https://www.three.co.uk/support/network-and-coverage/our-plans-to-switch-off-3g): completed technology sunset. - [Terms & conditions](https://www.three.co.uk/terms-conditions) - [Privacy portal](https://www.three.co.uk/privacy-safety/about-privacy) - [Ofcom Code of Practice](https://www.three.co.uk/terms-conditions/code-of-practice/code-of-practice) ## API Evangelist artifacts - [APIs.json](https://raw.githubusercontent.com/api-evangelist/three-uk/refs/heads/main/apis.yml) - [Review](https://raw.githubusercontent.com/api-evangelist/three-uk/refs/heads/main/review.yml): the full probe log behind the "no public API" finding. - [Conformance](https://raw.githubusercontent.com/api-evangelist/three-uk/refs/heads/main/conformance/three-uk-conformance.yml): CAMARA / GSMA Open Gateway posture, split between organisational and publication layers. - [Lifecycle](https://raw.githubusercontent.com/api-evangelist/three-uk/refs/heads/main/lifecycle/three-uk-lifecycle.yml): status page, service sunsets, absence of any API lifecycle. - [Well-known](https://raw.githubusercontent.com/api-evangelist/three-uk/refs/heads/main/well-known/three-uk-well-known.yml): every /.well-known/ probe and its status. - [Domain security](https://raw.githubusercontent.com/api-evangelist/three-uk/refs/heads/main/security/three-uk-domain-security.yml): TLS 1.3, HSTS 31536000, CAA set, SPF and DMARC (p=quarantine), no DNSSEC. - [Packages](https://raw.githubusercontent.com/api-evangelist/three-uk/refs/heads/main/packages/three-uk-packages.yml): the registries searched and the empty result. ## Notes for agents - There is nothing here to call. Do not synthesise a Three UK base URL, endpoint, or credential flow — none is published, and `api.three.co.uk` times out on 443. - Do not treat CAMARA specifications as Three UK artifacts. They are CAMARA Project documents; Three UK's implementations sit behind partner platforms with partner-issued credentials. - Authorization for Three UK's CAMARA APIs uses OpenID Connect and CIBA per the CAMARA specification, but that flow is operated by the channel partner. No Three UK OIDC discovery document exists (`/.well-known/openid-configuration` returns 404). - To integrate, start with an aggregator (JT Group, TMT.ID) or the GSMA Open Gateway programme — not with three.co.uk.