Single-endpoint report

Anthem Blue Cross Blue Shield Patient Access API (Elevance): endpoint report

Everything this project observed about this one endpoint, everything it did not observe, and what would change the result. Free to read, link, print and hand on; there is nothing here behind a sign-in and nothing to buy.

Built to print. Use your browser’s print or “Save as PDF” to keep a dated copy; the page carries its own address and observation date.

What was observed, and what was not

This report covers 4 checks. 0 ran. 2 were asked from every reporting vantage and answered by none. 2 were never asked, because nothing was retrieved for them to read. The three are different facts and none of them is a zero: a check that did not run publishes no number, no mark against this endpoint, and nothing below to act on.

What would change this

Nothing is listed here, because no check in this report ran. This project observed nothing about this endpoint on this run, and an absence is not a finding to act on.

If this does not match what you see

This run was not answered from any of 3 vantages on 1 network. A rule applied to one network's address space -- a bot filter, a geo rule, a rate limit -- reaches every vantage on that network at once, and nothing here can tell that apart from an endpoint being down. If this endpoint answers from your own network, that difference is the finding, and this project would rather publish it than keep this page as it stands.

Correct or dispute this record. There is no sign-in, no fee, and nothing to buy: this report is free to read, link, print and hand on, and this project collects nothing about the people who read it.

Where this came from

Listed on the organization's own publication of this base URL, not on a retrieved conformance document: base URL taken from the embedded link annotation of the row labelled 'Anthem Blue Cross Blue Shield' in the table 'FHIR Endpoints (Production Base URL)', section 'Patient Access API - Production Environment', of Elevance's Interoperability API Endpoint Support Document, Doc ID IO105, Version 15.0, effective 2025-11-18, status Active. Named for the operator and the brand rather than for a state on purpose: the table has thirteen brand rows and no state column, and the strings 'Ohio' and 'Wisconsin' appear nowhere in the document, so listing this URL once per state would put one address under several names. Two independent reviews, from the Ohio and Wisconsin rosters, reached this same row (recorded 2026-09-04). Published at https://www.anthem.com/content/dam/digital/developers-portal/Anthem-IOProviderDirectoryAndFormulary-API-Documentation.pdf. On the verification date this probe observed: HTTP 401 to an unauthenticated GET of /metadata, matching the two sibling per-brand paths since 2026-08-19. A Patient Access API may require authentication for member data, so this is not a defect claim; what it records is that the conformance document is not retrievable, so nothing this endpoint declares can be checked from outside. The document is served byte-identically from anthem.com and wellpoint.com (SHA-256 f383858d13a0d138c9ccfeba52bfe9d1fcd023f70e281b212623e2f6214d3b62); the anthem.com copy is cited here because it is the Anthem-branded publisher. No later re-check is recorded, so the date above is the last time anyone checked this entry against the live endpoint.

The same run, as data: this endpoint's JSON, what its CapabilityStatement declares, resource by resource, and every observation on record for it, with the dates it answered and the dates it did not.