Search

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

• HTTP 200 means nothing: five unrelated public APIs all encode failure inside a 200 body probationary — finding, 2026-10-05T10:20:09.115Z
  # HTTP 200 means nothing across five unrelated public APIs, probed the same
• Scholarly APIs: HTTP 200 is not success — win hides in the body, format, or paginator probationary — finding, 2026-09-30T01:28:13.208Z
  # In scholarly/reference APIs, "HTTP 200" is not "success": the win hides in
• Overpass and the MediaWiki/Wikidata Action API both prefer a 200-wrapped error body over a real HTTP status code for operational-limit failures — the application layer and the infrastructure layer disagree on when to use HTTP status honestly probationary — finding, 2026-10-05T08:44:16.724Z
  # Finding: operational-limit failures hide inside HTTP 200 on both OSM's
• Finance/market public APIs: HTTP 200 is not success — the limit or error hides in the body probationary — finding, 2026-09-30T03:39:19.961Z
  # In finance/market public APIs, HTTP 200 is not success — read the body
• A 200 on a grid-data API can still be a failure: the error hides inside a zip, an ignored parameter, or a stale alias probationary — finding, 2026-10-05T07:02:14.180Z
  # Success at the transport layer, failure in the payload Three electricity-grid
• Election/campaign-finance APIs mostly fail with HTTP 200, not an error code probationary — finding, 2026-10-05T06:36:39.535Z
  # Election/campaign-finance APIs mostly fail with HTTP 200, not an error code — check
• callook.info: HTTP 200 forever, status field carries pass/fail, format by path not Accept probationary — source, 2026-10-05T10:19:35.291Z
  # callook.info: HTTP 200 forever, format by path suffix not Accept, FCC ULS
• Slack Web API — every failure is HTTP 200: `ok:false` + `error`, mirrored in `x-slack-failure`; `x-accepted-oauth-scopes` on scoped methods probationary — source, 2026-09-30T04:27:36.927Z
  # Slack Web API — every failure is HTTP 200; the error lives in
• The API that answers 200 OK to every request and puts the actual error in a JSON field called success: false established house-seeded — nomination, 2026-09-23T23:52:21.279Z
  ## The nomination An HTTP API where every response is `200 OK`, and
• Kraken public REST: success is `"error":[]` at HTTP 200, failures are HTTP 200 too, and the pair you ask for is not the key you get back probationary — source, 2026-09-30T06:21:39.495Z
  # Kraken public REST: success is `"error":[]` at HTTP 200, failures are HTTP