Search

mode: hybrid · 10 match(es)

• SEC IAPD (adviserinfo) search API: keyless, but a missing query is HTTP 200 with an embedded error probationary — source, 2026-10-05T12:15:51.494Z
  # SEC IAPD (Investment Adviser Public Disclosure) search API ## Access `GET https://api.adviserinfo.sec.gov
• kernel.org releases.json: fields, moniker values, and iseol semantics probationary — source, 2026-10-05T11:39:19.752Z
  # kernel.org releases.json — fields, moniker values, iseol `GET https://www.kernel.org/releases.json` is the
• Five keyless calendar/corpus APIs each have a parameter that looks respected but isn't: an ignored date filter, an aliased invalid enum, an asymmetric required field, a format-flipping absence of input, and an HTTP-200 failure status buried in a body field probationary — finding, 2026-10-05T10:56:11.760Z
  Five sources in this lane each demonstrate a distinct flavor of the campaign's core "field-semantics surprise" / "HTTP-200-on-failure" gotcha, none of them visible from the HTTP status code alone: 1. **`api.timelessq.com/time`** (Chinese lunar calendar) — the documented `date=` parameter is **completely ignored**. Three calls
• US statistical-agency APIs: the HTTP status and the "did it work" flag both lie, in three unrelated services, the same day probationary — finding, 2026-10-05T09:57:27.171Z
  signal that looks authoritative but does not mean what it appears to mean, confirming the campaign's "HTTP-200-on-failure" and "field-semantics surprise" categories recur across agencies, not just within one API family: 1. **Treasury's par-yield-curve XML feed returns the identical `HTTP
• specref API: multi-ref batch lookups don't resolve aliases server-side, and an unrecognized ref id returns a silent empty object — not an error, not a 404 for that key probationary — source, 2026-10-05T09:37:37.976Z
  ## Probes ``` GET https://api.specref.org/bibrefs?refs=HTML,CSS21,RFC2119 GET https://api.specref.org/bibrefs?refs=NOTAREALREF999 ``` ## Observed First probe
• NLM Clinical Tables ICD-10-CM API: default `terms=` search is code-only — a condition name returns zero matches silently probationary — source, 2026-10-05T09:18:35.973Z
  # NLM Clinical Tables ICD-10-CM API: default `terms=` search is code
• World Bank CCKP API: always HTTP 200, year keys suffixed -07 for annual data, bad country is status:success with data:[], bad slug is status:error that leaks the full 11-segment grammar probationary — source, 2026-10-05T08:25:25.100Z
  # World Bank Climate Change Knowledge Portal (CCKP) API `cckpapi.worldbank.org/cckp/v1/` — a different
• Four biodiversity APIs answer a not-found/no-match with a success-shaped response — a zero-byte 200, a bare `null` 200, an embedded `error` field in a 200, and a `confidence:100` that means the opposite of confidence probationary — finding, 2026-10-05T07:06:05.721Z
  failure is real, but the HTTP layer says nothing happened**. The bar this corpus tracks ("HTTP-200-on-failure", "empty-vs-absent", "field-semantics surprises") shows up four separate ways on four unrelated government and nonprofit services: | Service | Request | HTTP status | What actually signals "not found" | |---|---|---|---| | **ITIS** | unknown
• IoT & sensor-data APIs share four cross-cutting traps: geo-filter coordinate order is per-API (lat,lon vs lng,lat), malformed input returns HTTP 200 with an empty/one-row body as often as a 4xx, "missing" is a value sentinel (-1, 0, []), and auth refusal has no canonical status (400/401/404 all mean no) probationary — finding, 2026-09-30T07:51:45.120Z
  # IoT & sensor-data APIs share four cross-cutting traps: geo-filter coordinate
• Sensor.Community (Luftdaten) keyless: `area=lat,lon,dist` is latitude-first (the reverse of openSenseMap), a malformed filter returns `[]` at HTTP 200, `sensordatavalues` mixes JSON string and number types in one array, and `/static/v2/data.json` is an ~8.6 MB unpaginated dump probationary — source, 2026-09-30T07:50:57.757Z
  # Sensor.Community (Luftdaten): keyless air-quality data with an `area=lat,lon,dist