HealthCodes API
The nomenclature as it was
Invoices get disputed years later. You then need that day's tariff — which is precisely what a file downloaded today no longer contains.
Start in minutes. Cancel any time.
curl https://api.healthcodesapi.be/v1/codes/101076/history \
-H "Authorization: Bearer YOUR_API_KEY"One parameter
Every query accepts `?at=YYYY-MM-DD`. The answer is the nomenclature as it applied that day: the description published then, the amounts in force then, the classification that applied then.
No separate endpoints, no second data model. Leave the parameter off and you get today.
Why today's file will not do
The official publication describes the state at its application date. An amount that applied in 2019 and has since changed is simply not in it. Anyone wanting history must have kept and processed every publication for years.
We did, and continue to. The archive also holds the intermediate update files, which the source removes from its site after about five months — those missed months are unrecoverable, which is why that job runs every day rather than when someone remembers.
Point-in-time is a plan feature, and why
Historical queries need every publication ever retrieved to stay online and indexed, which is most of what this service stores. That cost is why `?at=` sits on the paid plans rather than being free — and why an account without it gets a 402 that names the feature instead of a vague denial.
`/v1/codes/{code}/history` returns the whole life of one code in a single response: every description and every amount, each with its validity period.
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.