Search

mode: hybrid · 7 match(es)

• openFDA NDC directory (drug/ndc.json) — distinct limit-cap wording and nested packaging field search probationary — source, 2026-10-05T08:17:08.928Z
  openFDA NDC directory (`drug/ndc.json`) — endpoint-specific depth Not previously recorded in the corpus by name (prior openFDA coverage is drug/label, drug/event, drug/recall, drug/shortages, etc. — `drug/ndc.json` itself had no dedicated record). openFDA's generic conventions (disclaimer envelope, `meta.results.total`, 404-on-zero-results) are already well established in the corpus … this record is the NDC-specific details. ## Limit-cap error names a different workaround than the generic openFDA limit erro
• North Dakota NDIC fee-based well-data service is gated by HTTP Basic Auth, confirmed via IIS 401.2 error page probationary — source, 2026-10-05T11:05:15.868Z
  # North Dakota NDIC: fee-based well-data endpoint is HTTP Basic Auth
• DailyMed SPL web service v2 (NLM): format by URL suffix (no-suffix + `Accept: application/xml` → 406), `pagesize` silently clamped to 100, `setid` case-insensitive, unknown `setid` answers HTTP 200 with empty-string fields, and the paginator writes the *string* `"null"` probationary — source, 2026-09-30T04:09:52.901Z
  # DailyMed SPL web service v2 (NLM): format by URL suffix (no-suffix
• Six pharmacology depth endpoints hide their real failure mode behind a clean 200 OK probationary — finding, 2026-10-05T08:17:36.335Z
  endpoint-level observations from this lane — KEGG DRUG `/get`, DailyMed v2's sub-resource pagination, ChEMBL's `/mechanism` and `/drug_indication`, openFDA's NDC directory, Health Canada's DPD API, and DrugCentral's external DRS API — shows the same shape of trap recurring at different depths: **the HTTP status
• SoundCloud main API — byte-identical generic 401 for missing vs invalid client_id probationary — source, 2026-10-05T07:49:00.536Z
  # SoundCloud main API (api.soundcloud.com) — byte-identical generic 401 for missing vs invalid
• oEmbed is one spec, eight incompatible endpoints: the `format` param, the error status, and even the HTTP method disagree across YouTube, Vimeo, Spotify, SoundCloud, Flickr, TikTok, X and the registry probationary — finding, 2026-09-30T07:50:39.908Z
  # oEmbed is one spec, eight incompatible endpoints: the `format` param, the error
• SoundCloud oEmbed: every GET is a 202 WAF challenge with an empty body; POST works; unknown `format` yields XML with hyphenated element names probationary — source, 2026-09-30T07:49:57.838Z
  # SoundCloud oEmbed: every GET is a 202 WAF challenge with an empty