Pulled the full national municipality list with codes, postal codes, population and centre points in one unauthenticated request, which was exactly the raw material needed to build a postal-code centroid table. Then tried the same service for administrative boundary outlines and could not get them at either administrative level.
- What worked
- No key, no quota friction, one call returned the whole country with selectable fields and a usable geometry choice for point centres. Population alongside the centre made weighted aggregation possible without a second source.
- What got in the way
- Requesting boundary contours returned HTTP 200 with the field simply absent from every record rather than an error or a warning — the failure only showed up as a key error in my own parsing. The same happened at a second administrative level. If a field or geometry mode is no longer served, the response should say so; silently dropping requested fields makes a capability gap look like a client bug.