Researcher's works by ORCID

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

The works registered with a researcher's ORCID iD: their name as published, affiliations seen on their papers, the total number of works and the works themselves (same fields as /papers/v1/search), with type, year and keyword filters and sorts. Pass next_cursor back as cursor; null on the last page.

Every response includes credits_used: the credits this call cost.

Parameters

nametypedescription
orcidrequired string ORCID iD (16 digits with dashes, or the orcid.org URL). Example: 0000-0003-1419-2405
q string Keywords to search within the researcher's works.
type string Work type (journal-article, book-chapter, proceedings-article, posted-content, dataset...).
from_year integer Published in or after this year.
to_year integer Published in or before this year.
sort newest | citations | relevance | updated Order (default newest).
limit integer Works 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/author?orcid=0000-0003-1419-2405" \
  -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.