Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Bupa website screenshot

Bupa

Bupa is a United Kingdom headquartered international healthcare group that writes private medical insurance and also runs the clinics, dental practices, hospitals and aged-care homes that deliver the care it funds. It has no shareholders, is owned by the British United Provident Association Limited and reinvests its profits, and operates market units across the UK, Australia and New Zealand, Spain and Latin America (Sanitas, Bupa Chile), Turkiye, Poland, Hong Kong SAR, India and the Middle East, plus the Bupa Global international private medical insurance business. Its lines of business are health insurance, health provision and aged care rather than property and casualty or life, so the ACORD data standards that shape the rest of the insurance sector are absent from its published surface. Bupa's API posture is partner-gated: the group site bupa.com publishes no developer portal at all (developer, developers, docs and api subdomains do not resolve, and /developers, /api and /developer return 404), and the only first-party developer surfaces belong to market units. Bupa Australia runs a real Azure API Management developer portal at portal.api.bupa.com.au that returns HTTP 200 but lists no APIs publicly, instructing prospective consumers to contact the Bupa Integration Fabric Team to get access to API specifications; Bupa Chile runs apidoc.bupa.cl behind a Microsoft Entra ID login wall whose backend returns HTTP 401 to anonymous callers; and the Bupa Global portal host api-portal.bupaglobal.com no longer resolves. No public OpenAPI or Swagger definition, no Postman collection, no GraphQL or gRPC surface, and no event or webhook catalog could be confirmed anywhere on Bupa's public web estate as of 2026-07-25, and none of the four insurance API verbs — quote, bind, issue or FNOL — is exposed to unauthenticated developers.

human only

Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.

Kin Score

API Evangelist profiles Bupa the way a machine reads it — 5 machine-readable artifacts across 2 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.

Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Bupa scores 36.2/100 (thin), with a separate agent-readiness read of 10/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.

Kin Score

This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.

Kin Score Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 36.2/100 · thin
Contract Quality 0.0 / 25
Developer Ergonomics 10.4 / 20
Commercial Clarity 6.8 / 20
Operational Transparency 4.1 / 13
Governance 0.0 / 12
Discoverability 9.3 / 10
Regulatory · Health 10.1 / 15
Agent readiness — 10/100 · human only
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 15
MCP Server 0 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3

How we profile Bupa

Each block below is one kind of artifact we hold for Bupa. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.

APIs 2

Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.

Individual APIs this provider publishes, each with its own machine-readable definition.

Bupa Australia APIs (Integration Fabric)

The Bupa Australia API estate, published through an Azure API Management managed developer portal at portal.api.bupa.com.au and served from the api.bupa.com.au gateway host. The...

Portal de APIs Bupa (Bupa Chile)

The Bupa Chile API portal at apidoc.bupa.cl — an Angular single-page application that ships Swagger UI and renders API definitions fetched from the backend controller at https:/...

Security Posture 3

Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Bupa Authentication

oauth2/openIdConnect/apiKey · 3 schemes

SECURITY

Bupa Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Every other property we hold for Bupa — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.

Get Started 3

Portal, sign-up, and the first successful call

Documentation 2

Reference material describing how the API behaves

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 2

Pagination, idempotency, versioning, errors, and events

Build 2

SDKs, sample code, and the tooling you integrate with

Operate 2

Status, limits, changes, and where to get help

Commercial 2

Pricing, plans, and the legal terms of use

Company 3

The organization behind the API

← All providers · Data indexed from github.com/api-evangelist/bupa · machine-readable index on apis.io