HealthCodes API
Knowing what changed, without diffing anything
New codes, adjusted amounts, withdrawn procedures — as events, not as two archives you have to compare yourself.
Start in minutes. Cancel any time.
curl https://api.healthcodesapi.be/v1/changes?from=2026-01-01 \
-H "Authorization: Bearer YOUR_API_KEY"What a change is here
593,281 events since 1 January 2015, each with the date it took effect, the code it touched and what actually changed. Queryable by period, by code, or summarised by month.
`/v1/changes/months` returns every month that contains any change, with a count — enough to build a browsable archive without walking the whole feed.
What people build on it
The most common use is an alert: "these 14 codes your practice bills change on 1 January". That needs no accounting integration at all, just a list of codes and a periodic query. It is close to pure margin as a product.
The second is retrospective audit: last quarter's invoices against the nomenclature of the day each service was delivered. That needs the change feed to know which days matter.
Why the source cannot answer this
The official archives carry a 2018 timestamp regardless of their contents, so HTTP tells you nothing about whether anything moved. You have to download, unpack and compare. Across 1.7 million rows that is not a script you dash off.
We run that comparison daily and keep the result as events. What you fetch is the outcome, not the exercise.
HealthCodes API is an independent developer service and is not affiliated with or endorsed by RIZIV/INAMI. Official publications remain authoritative.
Simple pricing that scales with your application.
Every plan includes both languages, full history and change tracking.