Scholarly works search

GET https://api.api.sh/papers/v1/search
1 credit / call public data try it in the playground →

Searches 150M+ scholarly works (journal articles, books and chapters, conference papers, preprints, datasets, theses) by keywords, author or title: DOI, title, type, dates, authors with ORCID and affiliations, journal, publisher, volume/issue/pages, ISSN/ISBN, subjects, citation and reference counts, abstract (when deposited), licences, funders and full-text links. Filter by years, type, journal ISSN, funder, abstract or licence; sort by relevance, newest, citations or updated. Pass next_cursor back as cursor (valid for 5 minutes); null on the last page.

Every response includes credits_used: the credits this call cost.

Parameters

nametypedescription
q string Keywords. Example: crispr gene editing
author string Author name.
title string Title or citation text.
from_year integer Published in or after this year.
to_year integer Published in or before this year.
type journal-article | book | book-chapter | proceedings-article | posted-content | dataset | dissertation | report | monograph | reference-entry | peer-review | standard | edited-book | journal-issue | other Work type.
issn string Journal ISSN, e.g. 0028-0836.
funder_doi string Funder DOI, e.g. 10.13039/100000001 (NSF).
has_abstract boolean true: only works with an abstract.
open_license boolean true: only works with a licence.
sort relevance | newest | citations | updated relevance (default), newest, citations, updated.
limit integer Per page (default 20, max 100).
cursor string next_cursor from the previous page.

Every endpoint also takes fresh, raw, fields (see lean responses and caching).

Example

curl "https://api.api.sh/papers/v1/search?q=crispr+gene+editing" \
  -H "x-api-key: $APISH_KEY"

Response

A JSON object with the fields described above, plus raw (the source's own data), cached, fetched_at and credits_used. Errors return {"success": false, "error": "…"} with the HTTP status (see errors). A lookup that ran but found nothing (404) costs the price above; refused calls and errors on our side are free (what's charged).

The fastest way to see the full response is the playground: it runs this endpoint with your account and shows the exact JSON.