/pubmed/journals

POST /api/pubmed/journals

Price: 1 credit

Get a journal record from the NLM Catalog by NLM ID, ISSN, abbreviation, or title

How to use it

Look up a biomedical journal in the NLM Catalog by its NLM Unique ID, ISSN, ISO/MEDLINE abbreviation, or full title. Returns the journal record: title and alternate titles, MEDLINE abbreviation, ISSNs (print and electronic), publisher, place and country of publication, languages, broad subject terms, first and last publication years, indexing status, and the NLM Catalog web URL.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• journal string required — Journal identifier: NLM Unique ID, ISSN, ISO/MEDLINE abbreviation, or full title (examples: "0410462", "0028-0836", "N Engl J Med", "New England Journal of Medicine"; minLength: 1)

Response

• @type string (default: "PubmedCatalogJournal")
• nlmid string required
• uid string nullable
• medline_abbreviation string nullable
• issns array (default: [])
  • @type string (default: "PubmedJournalIssn")
  • issn string required
  • type string nullable
  • is_valid boolean (default: true)
• publisher string nullable
• place string nullable
• imprint string nullable
• dates_of_publication string nullable
• country string nullable
• languages array (default: [])
• broad_subject_terms array (default: [])
• alternate_titles array (default: [])
• start_year integer nullable
• end_year integer nullable
• is_active boolean (default: false)
• is_currently_indexed boolean (default: false)
• date_revised string nullable
• continuation_notes string nullable
• 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 — Journal 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.