Coverage policies, medical necessity criteria, drug coverage, and prior authorization requirements from 50+ payers across Commercial, Medicare Advantage, Medicaid, and ACA as structured JSON your systems can act on.
Request
{
"payer_id": "aetna",
"lob": "commercial",
"cpt_codes": ["63650", "95972"]
}Response 200
{
"results": [
{
"cpt_code": "63650",
"prior_auth_required": true,
"policies": [{
"policy_name": "Spinal Cord Stimulation"
}]
},
{
"cpt_code": "95972",
"prior_auth_required": false,
"policies": []
}
]
}50K+
Payer policies
50+
Payers & UM vendors
4
Lines of business
REST
JSON over HTTPS
A single determination often depends on a payer policy, the UM vendor's own criteria, and a CMS rule at once. We ingest all three and reconcile them.
01 · Clinical
Medical-necessity criteria and covered indications, per payer and line of business.
med_nec_tree02 · Payment
Coding, modifier and payment rules.
03 · Pharmacy
Tiers, step therapy and Part D coverage criteria, with brand and generic synonyms resolved.
drug_coverage[]04 · Authorization
Code-level PA requirements, tracked per payer and per line of business.
05 · Delegated
EviCore, Cohere, Carelon and peers.
06 · Federal
NCDs, LCDs and the Medicare Claims Processing Manuals.
Parsed daily into one structured schema
Reconciled across sources, dated, and linked back to the original document.
GET /v1/policiesThe same payer intelligence behind the NOF1 platform, built for software to consume.
List the payers and UM vendors NOF1 covers on each line of business, and resolve messy payer names from your eligibility or claims data to a single NOF1 payer ID.
Search clinical and pharmacy policies by free text, CPT/HCPCS code, payer, drug, or CMS LCD, ranked by relevance.
Get each policy's covered and excluded services, with coverage conditions as a structured AND/OR logic tree your software can evaluate.
Per-drug requirements from payer policies: step therapy, preferred alternatives, specialty and dosage limits, NDC codes, and FDA label IDs.
Check whether a payer requires prior auth for up to 10 CPT codes at once, with the policies that cover each code.
Medicaid policies and prior-auth answers carry the states they apply in, scoped to each payer's actual footprint.
Pass a line of business on each request, or search all four at once. The same payer ID works across all of them.
Employer-sponsored and other commercial health plans.
lob=commercialPrivate Medicare Advantage plans offered by commercial payers.
lob=medicareManaged Medicaid plans, with state-level policy coverage and state-specific prior-auth answers.
lob=medicaidIndividual marketplace (exchange) plans.
lob=acaBuilt for health tech platforms, provider organizations, and revenue-cycle teams that want payer policy inside their own products and workflows.
Know before submission whether a procedure needs prior auth for the patient's payer and plan type.
Surface a payer's medical necessity criteria at the point of care, not after a denial.
Show step therapy, preferred alternatives, and dosage limits for a drug under a payer's policy.
Compare how payers cover the same procedure or drug across lines of business.
No SDK to install. Any HTTP client works.
NOF1 enables the API for your organization.
Generate API keys yourself in the NOF1 APIs panel.
Send a Bearer token to any /v1 endpoint over HTTPS.
Narrow by line of business, payer, code, drug, or state.
Use structured JSON directly in your product or workflow.
A small, predictable surface with every parameter and response field documented.
Endpoints
https://api.nofone.io/v1/payersList payers
The NOF1 payer directory, filterable by line of business.
/v1/payers/matchMatch payer names
Resolve up to 25 payer names from your own data to NOF1 payers.
/v1/policiesSearch policies
Search by text, CPT/HCPCS code, payer, drug, LCD, or state.
/v1/policies/{policy_id}Get a policy
Coding, medical-necessity criteria trees, and drug coverage.
/v1/prior-auth/checkCheck prior authorization
Prior-auth requirements for up to 10 CPT codes per call.
Organization-scoped API keys you create, revoke, and rotate yourself.
Consistent response envelopes, typed fields, and machine-readable error codes.
The same payer ID works on every endpoint and every line of business.
Relevance-ranked text search plus code, payer, drug, LCD, and state filters.
Per-key limits reported on every response through standard headers.
Requests, errors, and latency by endpoint and key in the APIs panel.
Authentication, lines of business, Medicaid states, every parameter and response field.