/chembl/documents

POST /api/chembl/documents

Price: 1 credit

Get a ChEMBL source document by its identifier

How to use it

A document is the publication, patent or dataset a measurement was extracted from, and its id is the `document_id` carried on every activity and assay row. `doc_type` says which kind it is, so a patent carries `patent_id` and no journal while a paper carries `pubmed_id` and `doi`. Identifiers share one CHEMBL<number> namespace, and this route rejects non-document ids.

Parameters

• access-token string required

Request body

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

Response

• @type string (default: "ChemblDocument")
• id string (default: "")
• abstract string (default: "")
• authors string (default: "")
• doc_type string (default: "")
• journal string (default: "")
• journal_full_title string (default: "")
• year integer nullable
• volume string (default: "")
• issue string (default: "")
• first_page string (default: "")
• last_page string (default: "")
• doi string (default: "")
• doi_chembl string (default: "")
• pubmed_id string (default: "")
• patent_id string (default: "")
• contact string (default: "")
• source_id integer nullable
• chembl_release string (default: "")
• chembl_release_date 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 — Document 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.