Classifications
The structure codes are organised by, and a way to walk it.
| Method | Path | Returns |
|---|---|---|
GET | /v1/chapters | Chapters, with code counts |
GET | /v1/chapters/{id} | One chapter |
GET | /v1/chapters/{id}/codes | Codes in a chapter |
GET | /v1/articles | Articles |
GET | /v1/articles/{id} | One article |
GET | /v1/articles/{id}/codes | Codes under an article |
GET | /v1/sub-articles | Sub-articles, with parent and depth |
GET | /v1/sectors | Nomenclature groups |
Identifiers are strings
Chapter ids look like CH02, plus a P branch. Article ids are emphatically not numbers: 27/1, 35bis, 28§1 and 17ter are all real. Treat every identifier as an opaque string and percent-encode it in a URL.
Encoding
GET /v1/articles/27%2F1/codes
GET /v1/articles/35bissectors
What this API calls a sector is the source's nomenclature group (nomen_grp_n) — N01 is 'Consultations, visits and advice by doctors'. The route uses the word developers search for; this note says which source field it is, so there is no ambiguity.