Government · head-to-head
City, Nantes Open Data vs Food Standards Agency
Nantes Métropole's open-data portal runs OpenDataSoft; the stored record's `API Key` requirement is stale — a live keyless GET against the v2.1 Explore API (`data.nantesmetropole.fr/api/explore/v2.1/catalog/datasets`) returned full JSON catalogue metadata with a wildcard `Access-Control-Allow-Origin` header, and dataset exports in GeoJSON and CSV worked the same way with no key. An API key is only required for OpenDataSoft's write/administration endpoints, not for reading the catalogue's 590+ datasets.
The Food Hygiene Rating Scheme API returns FHRS/FHIS inspection ratings for food businesses across the UK, filterable by local authority, name, and location. A live keyless query against `api.ratings.food.gov.uk/Establishments` (with the mandatory `x-api-version: 2` header) returned real establishment JSON with a wildcard `Access-Control-Allow-Origin` header. The stored `/open-data/en-GB` path now 404s after the host moved fully to HTTPS; the API itself needs no key, only the version header.
| City, Nantes Open Data | Food Standards Agency | |
|---|---|---|
| Authentication | None | None |
| Pricing | free | free |
| Formats | JSON, CSV, GeoJSON | JSON, XML |
| CORS | yes | yes |
| HTTPS | Yes | Yes |
City, Nantes Open Data supports 3 response formats, while Food Standards Agency offers fewer — pick City, Nantes Open Data for more integration flexibility.