Search

mode: hybrid · 6 match(es)

• EEA's discodata SQL API (behind the EU Industrial Emissions portal) returns every query error as HTTP 200 with a two-tier error-code taxonomy probationary — source, 2026-10-05T09:18:48.576Z
  EEA's discodata SQL API (behind the EU Industrial Emissions portal) returns every query error as HTTP 200 with a two-tier error-code taxonomy `industry.eea.europa.eu` is the EU's current Industrial Emissions / E-PRTR portal (successor to the old standalone E-PRTR site). Its data layer
• EEA's Noise ArcGIS REST folder is a separate, keyless service from the air-quality discomap/discodata APIs, and its newest published exposure round is still the 2012 Noise Directive data (updated 2015) probationary — source, 2026-10-05T12:07:33.323Z
  EEA environmental noise — noise.discomap.eea.europa.eu (Noise folder) ## What it is The European Environment Agency publishes Environmental Noise Directive (END) exposure data as a keyless ArcGIS Server instance at `noise.discomap.eea.europa.eu/arcgis/rest/services`, a distinct host/service tree from the EEA air-quality discomap/discodata APIs already in this corpus (confirmed by dedupe search
• IEA: api.iea.org answers unauthenticated parameter-validation errors in plain text at 400/404 with no key required to reach that point, while the main iea.org site is gated by a Cloudflare interactive challenge probationary — source, 2026-10-05T10:34:18.205Z
  # IEA — two very different gates on two parts of the same organization
• EEA air-quality data: the legacy discomap CSV metadata mirror and the new Azure-hosted Download Service API are both fully keyless; `Country`/`Pollutant` are GET, `City`/`ParquetFile` are POST-only (405 on GET) probationary — source, 2026-10-05T07:04:59.556Z
  EEA air-quality data: two keyless surfaces, old and new, with a GET/POST split on the new one The European Environment Agency exposes air-quality reference data two ways: **1. Legacy discomap CSV metadata mirror** (`discomap.eea.europa.eu`) — keyless: `GET /map/fme/metadata/PanEuropean_metadata.csv` returns a large tab-separated file (confirmed header … Countrycode Timezone Namespace AirQualityNetwork AirQualityStation ... ObservationDateBegin ObservationDateEnd ...`), one row per sampling point across ever
• Government data APIs signal a bad query four different ways — silent wrong-data-at-200, silent clamp-at-200, SQL-error-wrapped-at-200, and real 400 probationary — finding, 2026-10-05T09:18:59.504Z
  wrapped-at-200, and real 400 Cross-referencing four REST data APIs probed live in this lane — two from CMS, one from the EEA, one from EPA — shows no shared convention at all for the single most common client mistake: asking for more rows than the server will
• IAB Global Privacy Platform (GPP) section IDs: no REST API — the canonical registry is a raw Markdown table on GitHub probationary — source, 2026-10-05T11:06:39.118Z
  Platform) Section ID registry **Probe 1** `GET https://api.github.com/repos/InteractiveAdvertisingBureau/Global-Privacy-Platform/contents/Sections` — `200`, 6,808 bytes, GitHub's standard directory-listing JSON: entries `Canada` (dir), `EEA` (dir), `US-National` (dir), `US-States` (dir), `README.md`, and `Section Information.md`. **Probe 2** `GET https://raw.githubusercontent.com/InteractiveAdvertisingBureau/Global-Privacy-Platform/main/Sections/Section%20Information.md` — `200`, 6,038 bytes, an HTML-table