What developer APIs does Fonteum offer?

Fonteum provides REST and hosted MCP access for public-record lookup, search, screening, and source context. FHIR R4 remains the healthcare interoperability surface. Bulk availability is manifest-led: only files with a delivered schema and compression format are listed.

Is authentication required to use the Fonteum FHIR API?

REST and MCP examples use an issued FONTEUM_API_KEY with Bearer authentication. Follow the current API authentication guide for access and rate-limit details; do not rely on a sample key.

What public records sources power the Fonteum API?

The active production registry spans healthcare, procurement, sanctions and watchlists, federal enforcement, intellectual property, securities filings, and global company registers. Results identify their named source and capture date; active registry status does not itself mean every family has loaded, complete, fresh, or displayable records.

How does Fonteum show source and capture context?

Where available, a result includes the named source, capture or snapshot date, methodology context, and limitations. This lets an integrator inspect the basis of a public-record fact without presenting the data as a derived risk score or endorsement.

Developer

Build on Fonteum’s public-records data

Fonteum provides REST and hosted MCP access to source-linked public records across healthcare, procurement, sanctions and watchlists, federal enforcement, and global company registers. FHIR R4 and bulk exports remain available where their documented contracts apply.

Reviewed by Dr. Jennifer Montecillo, MD, non-practicing medical reviewer. Last reviewed: June 2026 · Next review: December 2026

FHIR API

HL7 FHIR R4 US Core 6.1.0 provider directory. Practitioner, Organization, Location, PractitionerRole, HealthcareService — with SMART Backend Services auth and Bulk Data $export.

Read the reference→

Datasets

Browse source pages and manifest-led bulk exports. The manifest names each delivered file, its gzip compression, and its CSV columns.

Browse datasets→

Webhooks

Subscribe to provenance-stamped provider events. Receive HMAC-SHA256-signed POST notifications when LEIE or PECOS state changes for a tracked provider.

What you can build

Integration patterns

EHR and clinical workflow integrations — pull practitioner directory data into scheduling, referral, and credentialing modules using the FHIR PractitionerRole resource.
Compliance dashboards — surface OIG LEIE exclusion status and PECOS enrollment state for providers in your network using the webhook stream.
Research pipelines — use FHIR Bulk $export for supported provider resources and the machine-readable bulk manifest for files that are currently delivered; source and format availability vary.
Quality-scoring applications — combine MIPS performance scores, Care Compare star ratings, and HCRIS cost data to build custom provider quality indices.

Developer FAQ

Common questions

What developer APIs does Fonteum offer?: Fonteum provides REST and hosted MCP access for public-record lookup, search, screening, and source context. FHIR R4 remains the healthcare interoperability surface. Bulk availability is manifest-led: only files with a delivered schema and compression format are listed.
Is authentication required to use the Fonteum FHIR API?: REST and MCP examples use an issued FONTEUM_API_KEY with Bearer authentication. Follow the current API authentication guide for access and rate-limit details; do not rely on a sample key.
What public records sources power the Fonteum API?: The active production registry spans healthcare, procurement, sanctions and watchlists, federal enforcement, intellectual property, securities filings, and global company registers. Results identify their named source and capture date; active registry status does not itself mean every family has loaded, complete, fresh, or displayable records.
How does Fonteum show source and capture context?: Where available, a result includes the named source, capture or snapshot date, methodology context, and limitations. This lets an integrator inspect the basis of a public-record fact without presenting the data as a derived risk score or endorsement.
Where can I find the FHIR CapabilityStatement?: The FHIR CapabilityStatement is published at /api/fhir/metadata. It enumerates 5 USCDI v3 Provider resources: Practitioner, Organization, Location, PractitionerRole, and HealthcareService. The statement conforms to US Core 6.1.0 and includes SMART Backend Services security extensions.