How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

HealthSherpa Reference API

The Reference API from HealthSherpa — 3 operation(s) for reference.

HealthSherpa Reference API is one of 5 APIs that HealthSherpa publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Reference. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 3 operations across 3 paths, and defines 8 schemas. It is described by OpenAPI 3.2.0, at version 0.1.0.

Requests are made against a single base URL, https://api.one.healthsherpa.com.

3 operations 3 paths 8 schemas 3 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
0.1.0
Base URL
https://api.one.healthsherpa.com
Authentication
API Key
Resource Areas
1

Authentication & Security 1

HealthSherpa Reference API declares 1 security scheme for authenticating requests. An API key is passed in the header as x-api-key (ApiKeyAuth). By default, every request must be authenticated.

Paths & Operations 3

Across 3 paths, the API surfaces 3 operations — 3 GET. Each is listed below with its method, path, parameters, and response codes.

Reference 3
GET
/v1/reference/counties
List counties for a ZIP code
listCounties 1 param → 200400403404429500502503
GET
/v1/reference/issuers
List QHP issuers active in a state
listIssuers 2 params → 200400403404429500502503
GET
/v1/reference/providers
Search healthcare providers by name near a ZIP code
searchProviders 5 params → 200400403429500502503504

Schemas 8

The contract defines 8 schemas that model the data the API accepts and returns. The most detailed are ProviderEntity (13 properties), CountySummary (3 properties), ProvidersResponseMeta (3 properties), ProvidersResponse (2 properties). Each schema is shown below with its type and property counts.

CountiesResponse
object
1 property 1 required
ErrorResponse
object
Canonical error envelope returned by HealthSherpa-owned API endpoint, infrastructure filter, and backend service failures. The direct enrollment endpoints retu…
1 property 1 required
ProvidersResponseMeta
object
3 properties 3 required
IssuersResponse
object
1 property 1 required
CountySummary
object
3 properties 3 required
ProviderEntity
object
13 properties 1 required
ProvidersResponse
object
2 properties 2 required
IssuerSummary
object
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

healthsherpa-reference-api-openapi.yml Raw ↑

Other APIs HealthSherpa publishes across the network.

HealthSherpa Enrollment Sessions API
HealthSherpa Enrollments API
HealthSherpa Quotes API
HealthSherpa Utility API
Where this information came from

This is an independent, third-party profile of HealthSherpa Reference API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put 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.