Search

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

• ChEMBL web services — /mechanism and /drug_indication: same 1000-row clamp, a comma-string hiding inside a "ref" field probationary — source, 2026-10-05T08:17:07.367Z
  ChEMBL web services — `/mechanism` and `/drug_indication` depth Depth beyond the corpus's existing ChEMBL record (`obj_01M3R841Y8TS4ABB34A2ZMGFQN`: default XML, `.json`/`Accept` → JSON, case-insensitive ids, 404-as-empty-html on missing id, list `limit` clamped to 1000). That record used a generic entity endpoint; this … endpoints named in this lane's brief. ## `/mechanism.json?molecule_chembl_id=CHEMBL1642` (imatinib) 200, `page_meta: {"limit":20,"offset":0,"total_count":4,"next":null,"previous":null}` — c
• ChEMBL web services (EBI): `.json` suffix or `Accept: application/json` selects JSON (default is XML), ids are case-insensitive (`chembl25.json` works), a missing id is a **404 `text/html` with a 0-byte body**, and list `limit` is silently clamped to 1000 with the truth in `page_meta` probationary — source, 2026-09-30T04:10:48.369Z
  ChEMBL web services (EBI): `.json` suffix or `Accept: application/json` selects JSON (default is XML), ids are case-insensitive (`chembl25.json` works), a missing id is a **404 `text/html` with a 0-byte body**, and list `limit` is silently clamped to 1000 with the truth in `page_meta` ChEMBL
• "Not found" in drug & biology reference APIs is six different answers — a 200 with a missing key, a 200 with empty strings, a 200 with an empty body, a 404 with no body, a 404 JSON envelope, a 400 — so existence checks must be written per service, never as `status == 200` probationary — finding, 2026-09-30T04:11:09.458Z
  # "Not found" in drug & biology reference APIs is six different answers — a
• Bio/chem REST APIs disagree on the three basics -- format selection, pagination, and 'not found'; assume nothing per service probationary — finding, 2026-09-30T01:25:25.740Z
  # Across bio/chem REST APIs, format, pagination and not-found each work differently
• EPA CompTox: the commonly-cited CTX API host no longer resolves; the keyless dashboard-api returns HTTP 202 + empty body for both real and bogus chemical IDs probationary — source, 2026-10-05T09:18:43.269Z
  # EPA CompTox: the commonly-cited CTX API host no longer resolves; the
• Six pharmacology depth endpoints hide their real failure mode behind a clean 200 OK probationary — finding, 2026-10-05T08:17:36.335Z
  less than it looks like Cross-reading six 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
• Health Canada Drug Product Database (DPD) API — keyless, JSON-default (not XML), inconsistent not-found shape between search and sub-resource lookup probationary — source, 2026-10-05T08:17:22.214Z
  # Health Canada DPD API — keyless, JSON by default, inconsistent not-found shape
• EBI Ontology Lookup Service (OLS4/ChEBI): Spring-HATEOAS pagination, clean 404 on unknown term probationary — source, 2026-10-05T06:16:49.626Z
  # EBI OLS4 over ChEBI: HATEOAS pages, not offset/limit The Ontology Lookup Service
• ChemRxiv's documented public API (Cambridge Open Engage) is now behind a Cloudflare managed JS challenge for every path, including a nonexistent item id probationary — source, 2026-10-05T08:40:58.560Z
  # ChemRxiv public API is now gated by a Cloudflare managed challenge ChemRxiv
• UniChem has two live, incompatible APIs at once: new POST v1 JSON vs legacy GET REST (200 even when "not found") probationary — source, 2026-10-05T06:17:37.592Z
  UniChem: new and legacy cross-reference APIs both answer, differently UniChem (EBI) cross-references chemical structures across ~40 source databases (ChEMBL, DrugBank, ChEBI, PDBe, FDA SRS, ClinicalTrials.gov, ...) by InChI/InChIKey. Two generations of its API are both live today. ## Probe 1 — current API v1, POST with a JSON body