Changelog · InPlan

2026-10-30

API

InPlan API v1 is live

Eight endpoints answer which marketplace and Medicare Advantage plans list a provider. Every answer carries its evidence: source type, network tier, plan year and the date we read the data.

Endpoints in API v1
GET	/v1/providers/{npi}	Provider profile and a summary of the plans that list them.
GET	/v1/providers/{npi}/plans	Every plan that lists the provider. Filter by market, state and year.
GET	/v1/check	Is this provider in this plan? The answer with its evidence.
POST	/v1/check/batch	Up to 100 provider-plan pairs in one call.
GET	/v1/plans/{plan_id}	Plan details for marketplace and Medicare Advantage plans.
GET	/v1/plans/{plan_id}/providers	Providers a marketplace plan lists, by state, specialty or ZIP.
GET	/v1/coverage	Markets, states, insurers and plan counts, with dates.
GET	/v1/status	Health and data freshness. No key needed.

OpenAPI 3.1 file at api.inplan.io/openapi.json.
Keys sent as Authorization: Bearer ip_live_..., hashed at rest, with rate limits per key.
Errors in application/problem+json. A request_id on every response.

2026-10-30

DATA

Check providers against 1,300+ Medicare Advantage plans for 2027 by their contract-plan-segment ID. Each listing says whether the provider accepts new patients, and carries the date we read the plan's directory.

GET /v1/check?npi=1184617268&plan_id=H2526-001-000 "answer": "listed""plan_name": "DEVOTED CHOICE 001 OH (PPO)", "plan_year": 2027"accepting_new_patients": true"source": { "type": "plan_directory", "as_of": "2026-10-29" }

2026-10-30

API

Batch checks: 100 pairs in one call

On Builder and above, send up to 100 provider-plan pairs to POST /v1/check/batch. Each pair counts as one call. A bad pair returns its own error, and the rest of the batch still answers.

Read the batch guide →

What changed, and when.

InPlan API v1 is live

Medicare Advantage 2027 plans

Batch checks: 100 pairs in one call