/semanticscholar/papers/search

POST /api/semanticscholar/papers/search

Price: 5 credits

Search Semantic Scholar papers by query

How to use it

Search academic papers on Semantic Scholar by keyword query. Returns a list of papers, each with title, abstract, year, publication date, venue, citation/reference/influential-citation counts, fields of study, publication types, cross-reference ids (DOI, ArXiv, Corpus, MAG, DBLP, ACL, PubMed), authors, journal and publication-venue info, TLDR summary, BibTeX citation, open-access status and PDF link, and the Semantic Scholar web URL.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• query string required — Search query for papers (examples: "attention is all you need", "graph neural network"; minLength: 1)
• count integer required — Number of papers to return (min: 1)

Response

• @type string (default: "SemanticscholarPaper")
• id string required
• abstract string nullable
• year integer nullable
• published_at string nullable
• venue string nullable
• citation_count integer (default: 0)
• reference_count integer (default: 0)
• influential_citation_count integer (default: 0)
• fields_of_study array (default: [])
• s2_fields_of_study array (default: [])
• publication_types array (default: [])
• doi string nullable
• arxiv_id string nullable
• corpus_id string nullable
• mag_id string nullable
• dblp_id string nullable
• acl_id string nullable
• pubmed_id string nullable
• pubmed_central_id string nullable
• authors array (default: [])
  • @type string (default: "SemanticscholarPaperAuthor")
  • id string required
  • name string (default: "")
• journal object nullable
  • @type string (default: "SemanticscholarJournal")
  • name string nullable
  • volume string nullable
  • pages string nullable
• publication_venue object nullable
  • @type string (default: "SemanticscholarPublicationVenue")
  • id string nullable
  • name string nullable
  • type string nullable
  • alternate_names array (default: [])
  • url string nullable
• tldr string nullable
• bibtex string nullable
• is_open_access boolean (default: false)
• open_access_pdf_url 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 — 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.

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.