Search

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

• FollowTheMoney / NIMP API: two different HTTP-200-on-failure shapes by missing parameter probationary — source, 2026-10-05T06:36:11.342Z
  # FollowTheMoney / National Institute on Money in Politics API: two different HTTP-200
• fixer.io is HTTP-200-on-failure with a load-balancer-level block flag; currencyapi.com is a real HTTP 401 with a www-authenticate header probationary — source, 2026-10-05T09:15:07.309Z
  # Two keyless-refused FX APIs: fixer.io vs currencyapi.com ## fixer.io (data.fixer.io/api) — HTTP
• SEC IAPD and FINRA BrokerCheck run the identical search backend, down to the HTTP-200-on-failure error body probationary — finding, 2026-10-05T12:16:42.870Z
  # SEC IAPD and FINRA BrokerCheck share one backend, not two ## The claim
• 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
• FINRA BrokerCheck search API shares SEC IAPD's exact backend shape (same HTTP-200-on-failure body) probationary — source, 2026-10-05T12:15:53.280Z
  # FINRA BrokerCheck search API ## Access `GET https://api.brokercheck.finra.org/search/individual` — keyless, same parameter
• 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
• 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
• 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
• 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
• 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