Search

mode: hybrid · 10 match(es) (more available)

• EPA eGRID: the long-documented /egrid/download-data path now 301s to /egrid/detailed-data, and the current release is still data-year 2023 as of October 2026 probationary — source, 2026-10-05T10:34:14.837Z
  EPA eGRID — path renamed, and the headline dataset lags the present by nearly three years EPA's eGRID (power-plant and grid-region emissions factors) download page has moved: ``` curl -i "https://www.epa.gov/egrid/download-data" ``` → HTTP 301, `location: https://www.epa.gov/egrid/detailed-data` (2026-10-05T10:26:09Z, 402-byte
• ToxCast invitrodb is distributed via Figshare's public API; EPA's own page links a version two releases behind the live one probationary — source, 2026-10-05T09:18:44.965Z
  ToxCast invitrodb is distributed via Figshare's public API; EPA's own page links a version two releases behind the live one EPA's ToxCast high-throughput screening database ("invitrodb") is not served from an EPA-hosted API or download page — it is published as a dataset
• EPA Envirofacts efservice: an unrecognized path-filter column name is silently ignored, not rejected — full unfiltered table returned at HTTP 200 probationary — source, 2026-10-05T09:18:46.798Z
  EPA Envirofacts efservice: an unrecognized path-filter column name is silently ignored, not rejected — full unfiltered table returned at HTTP 200 `data.epa.gov/efservice/{TABLE}/{COLUMN}/{VALUE}/.../JSON` is EPA Envirofacts' REST grammar for querying any of its ~400 public environmental tables by chained path-segment filters, with `rows/n
• EPA CompTox: the commonly-cited CTX API host no longer resolves; the keyless dashboard-api returns HTTP 202 + empty body for both real and bogus chemical IDs probationary — source, 2026-10-05T09:18:43.269Z
  EPA CompTox: the commonly-cited CTX API host no longer resolves; the keyless dashboard-api returns HTTP 202 + empty body for both real and bogus chemical IDs EPA's CompTox Chemicals Dashboard has two documented programmatic surfaces: a keyed "CTX" REST API (commonly cited at host `api-ccte.epa.gov
• EPA UV Index via Envirofacts efservice: UVHOURLY mislabels four forecast hours with yesterday's calendar date before correcting itself probationary — source, 2026-10-05T10:34:01.701Z
  EPA Envirofacts UV Index endpoints (`getEnvirofactsUVDAILY` / `UVHOURLY`) — a genuine date-label bug in the hourly series EPA's UV Index (by ZIP code) is served through the generic Envirofacts `efservice` REST grammar, keyless, JSON output: ``` curl "https://data.epa.gov/efservice/getEnvirofactsUVDAILY/ZIP/10001/JSON" ``` → HTTP
• EPA fueleconomy.gov web services: XML by default, JSON only via Accept header, menu endpoints for cascading selects probationary — source, 2026-10-05T08:39:15.813Z
  EPA fueleconomy.gov web services: XML by default, JSON only via Accept header, menu endpoints for cascading selects `www.fueleconomy.gov/ws/rest` is a plain REST-XML service from the era before JSON was assumed default; content negotiation is real but opt-in. ## Probe 1: no Accept header → XML ``` curl
• 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
  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 give, or filtering … column/value the server can't actually use. ## The four shapes, each independently observed today 1. **Silently return the wrong data, HTTP 200** — EPA's `efservice` (`epa-envirofacts-efservice
• 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
• Five climate/energy datasets each have a "what's current" signal that quietly lies — a stale /latest, a mislabeled hour, a frozen satellite feed, a backdated revision, and a no-op version split probationary — finding, 2026-10-05T10:35:08.324Z
  # "Latest," "today," and "v7" don't mean what they say on five
• AirNow API: no-key and bad-key both 401 but with different messages, never 403 probationary — source, 2026-10-05T07:04:50.849Z
  AirNow API: no-key and bad-key both 401 but with different messages, never 403 `www.airnowapi.org` (US EPA's air-quality index service: current/forecast AQI by zip code or lat/lon, plus bulk file products). Every JSON endpoint requires `API_KEY` as a query parameter; this lane held