POST /api/chembl/molecules/drug-indications
Price: 5 credits
Get the diseases one ChEMBL molecule is indicated for, with the phase reached for each
Rows come from drug labels and clinical trial registries, so a compound that never entered the clinic answers with an empty list, exactly as an unknown id does. The phase is per indication: a molecule approved for one disease can sit at phase 2 for another, which is what `max_phase_for_indication` carries. Each disease is named twice, as a MeSH heading and as an ontology term, and either may be absent.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)molecule string required — ChEMBL molecule identifier, or a ChEMBL page URL containing one (examples: "CHEMBL25"; minLength: 1)mesh_id string nullable — Keep only indications carrying this MeSH identifier (examples: "D010146"; minLength: 1)efo_id string nullable — Keep only indications carrying this EFO or ontology identifier (examples: "EFO:0003843"; minLength: 1)min_max_phase_for_indication number nullable — Lowest clinical phase the molecule reached for the indication, 4 meaning approved (examples: 4; min: 0; max: 4)include_salts_and_mixtures boolean — True also returns indications recorded for salts and mixtures whose parent is this molecule, False keeps only indications recorded for the molecule itself (default: true)count integer required — Max number of results (min: 1; max: 1000)@type string (default: "ChemblDrugIndication")id string (default: "")molecule_id string (default: "")parent_molecule_id string (default: "")mesh_id string (default: "")mesh_heading string (default: "")efo_id string (default: "")efo_term string (default: "")max_phase_for_indication number nullablereferences array (default: [])@type string (default: "ChemblReference")type string (default: "")id string (default: "")url string (default: "")422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.412 — The entity was not found, or a precondition failed Retrying will not help: either the entity does not exist, or the input points at a different one.429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.X-Retry-After — Seconds to wait before retrying. Present only on 429.