What the catalogue's APIs actually return. Every response field from 978 machine-readable specs, grouped two ways: by the real-world identifiers they carry (which tells you what each API is about and what it can be joined with), and by name variants that mean the same thing.
Click an identifier to see its spellings and the APIs that expose it. Bars show the number of APIs. For an identifier that contains others, the count reads direct / with children: APIs naming it, then APIs naming it or any identifier inside it (SIREN alone, then SIREN or SIRET or VAT…). The pale part of the bar is the extra reach. Indented rows sit inside the one above (SIRET belongs to a SIREN, a commune to a département).
| API | Publisher | Main entity |
|---|
Each API gets one main entity, decided by its shallowest identifier: path parameters such as {siren} first, then top-level fields. Ties go to the most specific entity, so an API with both a SIRET and a commune code counts as a company API. Bar shading shows confidence.
| API | Publisher | Main entity | Decided by | Also |
|---|
id, objectid, gml_id, gid…) were kept out of the identifier map: they only mean something inside one dataset.