Single-endpoint report

Health Care Service Corporation Provider Directory API: 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 printed verbatim on Health Care Service Corporation's own interoperability site, on the Provider Directory API page, as 'API endpoint base url: https://api.hcsc.net', with the instruction to substitute it for {environmentBaseUrl} in the paths the downloadable API spec gives. The page covers the Blue Cross and Blue Shield plans HCSC operates in Illinois, Montana, New Mexico, Oklahoma and Texas, so the entry is named for the corporation rather than for the Texas brand: one address serves five state plans and nothing in it distinguishes them. Blue Cross and Blue Shield of Texas's own domain publishes no interoperability or developer page at all; its 583-URL sitemap contains none (recorded 2026-08-19). Published at https://interoperability.hcsc.com/s/provider-directory-api. On the verification date this probe observed: HTTP 500 to a GET of /metadata. TLS is clean from this vantage with and without certificate verification, so the host is live and the server is erroring at the conformance path FHIR R4 requires every server to publish. The page prints this string as a base URL to substitute into spec paths rather than as a FHIR base, which is recorded here rather than repaired: no other address for this surface is printed, and constructing one would be a guess. 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.