Skip to content
FonteumPublic-records evidence
API · v1 · SNAPSHOT DIFF

Snapshot diff

Inspect the planned field-diff response shape. This endpoint currently returns labelled illustrative changes, not live retained diffs or signatures on changed values.

Status: this endpoint currently returns a clearly labelled stub (_stub: true, every change _illustrative: true). The response shape is production-final. No date is promised here for replacing the illustrative payload with retained snapshot data.

Authentication

Send Authorization: Bearer <key>. The read-only sample key fnt_DEMO_PUBLIC_V1 is limited to 20 requests/minute and 100 requests/day per trusted source IP; account fnt_ keys use their configured limits. A missing or unknown key returns 401.

Request

FONTEUM_API_KEY="${FONTEUM_API_KEY:-fnt_DEMO_PUBLIC_V1}"
curl -X POST "https://api.fonteum.com/v1/snapshots/diff" \
  -H "Authorization: Bearer $FONTEUM_API_KEY" \
  -H "Content-Type: application/json" \
  --data '{
  "dataset": "nppes",
  "from_snapshot": "2026-04-01T00:00:00Z",
  "to_snapshot": "2026-05-01T00:00:00Z",
  "fields": ["taxonomy", "addresses"]
}'
  • dataset — required dataset id (e.g. nppes).
  • from_snapshot / to_snapshot — required ISO 8601 timestamps or snapshot ids.
  • fields — optional field allow-list; defaults to ["taxonomy", "addresses"].

Response

In the labelled stub, a changes[] record can carry before / after values and the nullable provenance fields present in the planned shape, plus a change_type of added, removed, or modified. A summary object totals the three. Missing provenance fields must not be inferred. The machine-readable schema lives at /api/v1/snapshots/diff/_schema.json (in-repo).

Back to chain integrity status

What’s on file, by the numbers

Platform snapshot · 2026-07-25

13.4Mproviders & companiesProviders, organizations, owners, and facilities on file
26.2Msource-linked factsSource-linked field facts in the dated platform snapshot
90sources with dataDistinct snapshot source IDs with at least one positive record count
79fresh sourcesDistinct source IDs whose latest positive-data snapshot falls within the preceding 45 days
111sources integratedActive registry rows; integration does not establish a load
13state Medicaid jurisdictionsDistinct states represented in the state-exclusions serving table

Integrated, with-data, and fresh-observation counts are separate. No platform-wide source-completeness count is published. Completeness is source-specific and must be evaluated against the named source's expected scope. State coverage is a separate jurisdiction measure.

Source authority is record-specific

Use the issuer named on the record.

Fonteum spans federal, state, and global public publishers. A source page or returned record identifies its issuer and dataset where that metadata is available. A platform registry count does not assign every page to one authority or establish loaded, fresh, or complete coverage.

Browse source records and their stated limitations →

Reproducible by design

Inspect the evidence each published figure actually supplies.

Source and date

Research pages expose the named public file and observation date where those fields are available. Source-file SHA-256 coverage is separate; facts do not currently link deterministically to signatures.

Available derivation

Studies with a retained release and committed derivation link the SQL or method used. Other studies state the evidence and reproduction limits they actually have.

Daily observations

Dated table row-count observations can detect local drift. They do not imply that an upstream publisher released or Fonteum ingested new data that day.

Named medical review

Reviewed by Jennifer Montecillo, MD, medical reviewer. Non-practicing medical reviewer.

Read the full provenance and attestation methodology →

Request access