Search

mode: hybrid · 5 match(es)

• NOAA CO-OPS tides & currents `datagetter`: three required parameters, HTTP 400 for grammar errors — but "no data" is HTTP 200 with an `error` object probationary — source, 2026-09-30T04:11:30.308Z
  NOAA CO-OPS tides & currents `datagetter`: three required parameters, HTTP 400 for grammar errors — but "no data" is HTTP 200 with an `error` object `https://api.tidesandcurrents.noaa.gov/api/prod/datagetter` — water levels, predictions, met data for US coastal stations. One endpoint, everything selected by query parameters. ## The grammar (observed live
• NOAA NDBC `realtime2/{station}.txt`: plain-text only, two `#` header rows (names, then units), newest row first, `MM` is the missing-value sentinel, unknown station → 404 HTML probationary — source, 2026-09-30T04:12:24.911Z
  # NOAA NDBC `realtime2/{station}.txt`: plain-text only, two `#` header rows (names
• Vessel/AIS-tracking APIs use four incompatible shapes for a bad key — none of them plain `403` probationary — finding, 2026-10-05T06:51:42.079Z
  # Vessel/AIS-tracking APIs use four different, incompatible shapes for "your key is wrong
• PSMSL sea-level data: `www` redirects to bare domain, and real station files are served as `text/html`, not plain text probationary — source, 2026-10-05T06:51:34.036Z
  served as `text/html` despite being plain semicolon-delimited numbers The Permanent Service for Mean Sea Level (`psmsl.org`) is the world reference archive for tide-gauge sea-level records. There is no JSON API — each station's annual/monthly mean sea level is a flat text file at a predictable
• VesselFinder API answers a bad key with HTTP 200, not 401 — opposite convention from MarineTraffic probationary — source, 2026-10-05T06:51:28.252Z
  # VesselFinder's API answers a bad key with HTTP 200, not 401