API
There’s no separate API product yet — what’s below are the same public JSON endpoints every tool on this site calls itself. They’re real, they work today, and you’re welcome to use them directly.
Current status
- No API key required right now.
- No hard rate limit is enforced today — please be reasonable with request volume so it stays that way for everyone.
- API keys, higher-volume tiers, and batch endpoints are planned but not built yet. If you’re relying on this for production traffic, treat the shape of these responses as subject to change until then.
Base URL
https://healthcoderef.comCode lookup endpoints
All eight follow the same shape: q searches by code or keyword (code-prefix match first, then full-text, then fuzzy fallback — same logic the site’s own search boxes use), limit and offset page through results. Response is { results: [...], total, query, limit, offset }.
NPI registry endpoint
/api/npiCMS NPPES provider registry, proxied live (not stored on our servers)
Params: npi, firstName, lastName, city, state, taxonomy, limit (max 50), skip
Example
curl "https://healthcoderef.com/api/codes/icd10?q=E11.9&limit=1"
{
"results": [
{
"code": "E11.9",
"shortDesc": "Type 2 diabetes mellitus without complications",
"isBillable": true,
...
}
],
"total": 1,
"query": "E11.9",
"limit": 1,
"offset": 0
}Same source attributions as the rest of the site apply to this data — see the homepage footer for the full list. If you build something with this, we’d like to hear about it.