/pubmed/articles

POST /api/pubmed/articles

Price: 1 credit

Get a PubMed article by its PMID

How to use it

Get full details of a biomedical article from PubMed by its PMID. Returns title, abstract, authors (with affiliation and ORCID), journal info, publication year and date, publication model and types, keywords, MeSH headings, chemicals, grants, registered data banks, conflict-of-interest statement, cross-reference ids (PMID, PMCID, DOI), processing history, and the PubMed web URL.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• id string required — PubMed identifier (PMID) (examples: "23467347", "30684591"; minLength: 1)

Response

• @type string (default: "PubmedArticle")
• pmid string required
• doi string nullable
• pmcid string nullable
• pii string nullable
• vernacular_title string nullable
• abstract string nullable
• author_string string nullable
• last_author string nullable
• authors array (default: [])
  • @type string (default: "PubmedAuthor")
  • full_name string nullable
  • last_name string nullable
  • first_name string nullable
  • initials string nullable
  • orcid string nullable
  • affiliation string nullable
• journal object nullable
  • @type string (default: "PubmedJournal")
  • iso_abbreviation string nullable
  • medline_abbreviation string nullable
  • nlmid string nullable
  • issn string nullable
  • essn string nullable
  • issn_linking string nullable
  • volume string nullable
  • issue string nullable
  • pages string nullable
  • country string nullable
  • pub_date string nullable
• pub_year integer nullable
• pub_date string nullable
• epub_date string nullable
• language string nullable
• pub_model string nullable
• publication_status string nullable
• pub_types array (default: [])
• keywords array (default: [])
• mesh_headings array (default: [])
  • @type string (default: "PubmedMeshHeading")
  • descriptor_name string required
  • descriptor_ui string nullable
  • is_major_topic boolean (default: false)
  • qualifiers array (default: [])
• chemicals array (default: [])
  • @type string (default: "PubmedChemical")
  • name string required
  • registry_number string nullable
• grants array (default: [])
  • @type string (default: "PubmedGrant")
  • grant_id string nullable
  • agency string nullable
  • acronym string nullable
  • country string nullable
• data_banks array (default: [])
  • @type string (default: "PubmedDataBank")
  • name string required
  • accession string required
• coi_statement string nullable
• citation_subset string nullable
• history array (default: [])
  • @type string (default: "PubmedHistoryEvent")
  • status string required
  • date string required
• date_completed string nullable
• date_revised string nullable
• record_status string nullable
• pmc_ref_count integer (default: 0)
• web_url 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 — Article 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.