/chembl/targets

POST /api/chembl/targets

Price: 5 credits

Get a ChEMBL target by its identifier

How to use it

Identifiers share one CHEMBL<number> namespace with molecules, assays and documents, and this route rejects anything that is not a target. A target is not always a single protein: `target_type` also covers protein complexes, cell lines, tissues and whole organisms, and only protein-backed types carry `components` with their UniProt accessions. Use those accessions to join to sequence databases; `id` is what the activity endpoints take.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• target string required — ChEMBL target identifier, or a ChEMBL page URL containing one (examples: "CHEMBL1824", "https://www.ebi.ac.uk/chembl/explore/target/CHEMBL1824"; minLength: 1)

Response

• @type string (default: "ChemblTarget")
• id string (default: "")
• name string (default: "")
• target_type string (default: "")
• organism string (default: "")
• tax_id string (default: "")
• is_species_group boolean nullable
• components array (default: [])
  • @type string (default: "ChemblTargetComponent")
  • component_id string (default: "")
  • accession string (default: "")
  • description string (default: "")
  • type string (default: "")
  • relationship string (default: "")
  • synonyms array (default: [])
    • @type string (default: "ChemblTargetComponentSynonym")
    • name string (default: "")
    • type string (default: "")
  • cross_references array (default: [])
    • @type string (default: "ChemblCrossReference")
    • source string (default: "")
    • id string (default: "")
    • name string (default: "")
• cross_references array (default: [])
  • @type string (default: "ChemblCrossReference")
  • source string (default: "")
  • id string (default: "")
  • name string (default: "")

Errors

• 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 — Target not found 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.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-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.