Data Sources
VeriflowAPI aggregates and normalizes data from multiple authoritative government sources. This page explains what each source covers, how frequently data is refreshed, and what happens when a source is temporarily unavailable.Federal Sources
These sources are checked on every verification request regardless of state.NPPES NPI Registry
The National Plan and Provider Enumeration System is the federal database of all healthcare providers who have been assigned a National Provider Identifier.
The NPPES database is the foundation of every verification. Even when a state board is temporarily unavailable, NPI data ensures you always receive a meaningful baseline response.
OIG Exclusion List
The Office of Inspector General maintains a list of individuals and entities excluded from participation in federal healthcare programs (Medicare, Medicaid, etc.). Hiring or contracting with an excluded provider can result in significant civil penalties.
If
oig_excluded is true, the provider must not be employed or contracted by any entity receiving federal healthcare funding. This is a hard disqualifier in most onboarding workflows.
State Sources — Live
Deep state license data is available for eight states today. Texas and New York are live per-query scrapes; the rest are full daily mirrors. Any other state returnsstatus: "unsupported_state" on live keys — we never fabricate data we don’t have.
Texas Medical Board
Florida Department of Health (MQA)
Illinois IDFPR
Washington Department of Health
Colorado DORA
Connecticut DCP
Alabama Board of Medical Examiners
New York Office of the Professions
New York licenses do not “expire”; the triennial registration does. A currently registered licensee returns
status: "active"; a lapsed registration returns status: "expired". For physicians, disciplinary actions are published by the NYS Department of Health (OPMC) rather than the Office of the Professions, so enforcement flags on 060 (Medicine) records come from that separate source.
What happens when a source is down
Government websites experience downtime — planned maintenance, traffic spikes, infrastructure migrations. VeriflowAPI is architected to handle this gracefully. When a source is unavailable during a request:- VeriflowAPI serves the most recent cached data for that source
- The response includes
"source_live": falseand"cached": true - The
cache_expires_atfield tells you when fresh data will next be fetched - Our monitoring system detects the outage and begins retry attempts automatically