Health tech · search · matching · intake
Network data in your product, without the pipeline.
Add plan-by-plan network answers to provider search, patient matching and intake forms. Call the API for live lookups, or load data files into your warehouse.
How it usually starts
“We just need to know which plans list this provider.”
- 1Someone writes a script to read one insurer’s directory.
- 2Then a second insurer, in a different format, and a matching step to tie listings to NPIs.
- 3Then plan years turn over, and the script needs a team.
- 4Or: one API key, 650M+ provider-plan links already matched and dated.
Three places network data fits.
Most platforms start with one and add the others. Each uses the same answer format, so your UI code stays the same.
SEARCHFilter results by the user's planList the providers a marketplace plan's directory includes, then apply your own ranking and distance rules.GET /v1/plans/{plan_id}/providers
MATCHINGShow network chips on a provider cardFor a provider you already show, list every plan that includes them, with tier and date.GET /v1/providers/{npi}/plans
INTAKECheck the pair a patient entersWhen a patient names their plan and their doctor, check that one pair and store the answer.GET /v1/check?npi=…&plan_id=…
For your engineers
Plan in, providers out.
Plan-to-provider search returns the providers a marketplace plan's directory lists, each with its network tier and the date the directory was read.
OpenAPI 3.1 specTypical response < 50 msRequest ID on every responseRate-limit headersHealth check: GET /v1/statusData summary: GET /v1/coverage
curl https://api.inplan.io/v1/plans/29276OH0970001/providers \
-H "Authorization: Bearer $INPLAN_KEY"{
"plan_id": "29276OH0970001", "plan_year": 2026,
"plan_name": "Anthem Bronze Pathway 10600 …",
"providers": [
{
"npi": "1184617268",
"name": "Michael B. Williard, MD",
"primary_specialty": "Orthopedic Surgery",
"network_tiers": ["PARTICIPATING"],
"locations": [{ "city": "Gahanna", "state": "OH" }]
},
…
],
"source": { "type": "insurer_directory", "as_of": "2026-07-27" }
}API calls or data files?
Choose by how your product uses the data. Both carry the same fields and evidence, and many teams use both.
| Question | API | Data files |
|---|---|---|
| BEST FOR | Live lookups while a user waits | Joins with your own tables, analytics, offline matching |
| SPEED | Typical response under 50 ms; batch of up to 100 pairs | As fast as your own database |
| PRICE | Free to $599 a month by call volume; Scale is custom | $299 a state, $1,499 national, $199 a month to refresh |
| FRESHNESS | Current data on every call, with its read date | Every row keeps its read date; each refresh sends a new copy of your files |
What your platform gains.
7.7Mprovider records behind every lookup
2markets, marketplace and Medicare Advantage, in one format
0patient data sent to us or stored
Ship network data this sprint.
Growth · $599 /mo150,000 calls, plan-to-provider search, priority support
Scale · CustomHigher volume, bulk data files, SLA
Compare all plans