Research Papers citing works API

Use the Research Papers citing works API to retrieve citing works and the citation information published by the source. Identify a cited work by DOI or OpenAlex work ID, then filter later citing works by years, type, open access or text; paging stops at 10,000 results. Trace later work citing a publication, inspect citation relationships, or expand a literature review from a known paper. Citation direction is forward from the selected work to later citing records, not the selected paper’s own bibliography. The detail page provides request and response examples, supported parameters, and usage pricing.

Selected price
$0.002 / billing creditPublished pricing
Sellers / implementations
1 / 1
Requests · 30d
—Loading...
Success rate · 30d
—Loading...

Run sends a real API request. Charges follow the published API contract.

Request parameters
Optional parameters (15)
DOI of the cited work (or its doi.org URL). Pass this or `work_id`.
Work id of the cited work (the `work_id` of a result, e.g. `W2919115771`), for works without a DOI; instead of `doi`.
Keywords to search within the citing works.
Citing work type (article, review, preprint, book-chapter, conference-paper, dataset, dissertation...).
Published in or after this year.
Published in or before this year.
true: only open-access citing works.
Order (default citations: most cited first).
Works per page (default 20, max 100).
Page number. Pass `next_page` from the previous response; null on the last page.
0 leaves out the bulky `raw` source blocks (often 10-30x smaller).
Comma-separated fields to return, e.g. `posts.id,posts.title`. Call metadata is always included.
1 skips the 24-hour cache and fetches live.
JSON only for this OpenAny product. Omit output or use json; CSV and NDJSON exports are not exposed.
Native CSV/NDJSON record selector; it has no effect on this JSON-only product.

Sample response

{
  "applied_filters": [],
  "attribution": "Citation graph: OpenAlex (openalex.org), CC0",
  "cached": false,
  "cited": {
    "citations": 84572,
    "doi": "10.1038/nature14539",
    "title": "Deep learning",
    "work_id": "W2919115771",
    "year": 2015
  },
  "count": 20,
  "credits_used": 1,
  "items": [
    {
      "authors": [
        {
          "institutions": [
            "Google DeepMind (United Kingdom)"
          ],
          "name": "David Silver",
          "orcid": "0000-0002-5197-2892",
          "position": "first"
        },
        {
          "institutions": [
            "Google DeepMind (United Kingdom)"
          ],
          "name": "Aja Huang",
          "orcid": "0000-0002-2476-9194",
          "position": "middle"
        },
        "… 18 more"
      ],
      "authors_count": 20,
      "citations": 15843,
      "container_title": "Nature",
      "doi": "10.1038/nature16961",
      "issn": [
        "0028-0836",
        "1476-4687"
      ],
      "issue": "7587",
      "language": "en",
      "open_access": {
        "is_oa": false,
        "status": "closed",
        "url": null
      },
      "page": "484-489",
      "published": "2016-01-26",
      "publisher": "Nature Portfolio",
      "title": "Mastering the game of Go with deep neural networks and tree search",
      "type": "article",
      "url": "https://doi.org/10.1038/nature16961",
      "volume": "529",
      "work_id": "W2257979135",
      "year": 2016
    },
    {
      "authors": [
        {
          "institutions": [
            "Radboud University Medical Center"
          ],
          "name": "Geert J. S. Litjens",
          "orcid": "0000-0003-1554-1291",
          "position": "first"
        },
        {
          "institutions": [
            "Radboud University Medical Center"
          ],
          "name": "Thijs Kooi",
          "orcid": "0000-0001-7701-7837",
          "position": "middle"
        },
        "… 7 more"
      ],
      "authors_count": 9,
      "citations": 15404,
      "container_title": "Medical Image Analysis",
      "doi": "10.1016/j.media.2017.07.005",
      "issn": [
        "1361-8415",
        "1361-8423",
        "… 1 more"
      ],
      "issue": null,
      "language": "en",
      "open_access": {
        "is_oa": true,
        "status": "bronze",
        "url": "https://ars.els-cdn.com/content/image/1-s2.0-S1361841517301135-fx1_lrg.jpg"
      },
      "page": "60-88",
      "published": "2017-07-26",
      "publisher": "Elsevier BV",
      "title": "A survey on deep learning in medical image analysis",
      "type": "review",
      "url": "https://doi.org/10.1016/j.media.2017.07.005",
      "volume": "42",
      "work_id": "W2592929672",
      "year": 2017
    },
    "… 18 more"
  ],
  "next_page": 2,
  "page": 1,
  "query": null,
  "sort": "citations",
  "total": 84140
}

Response result

Response structure

Inferred from examples
  • applied_filtersunknown[]
  • attributionstring
  • cachedboolean
  • citedobject
    • citationsinteger
    • doistring
    • titlestring
    • work_idstring
    • yearinteger
  • countinteger
  • credits_usedinteger
  • items(object | string)[]
    • authors(object | string)[]
      • institutionsstring[]
      • namestring
      • orcidstring
      • positionstring
    • authors_countinteger
    • citationsinteger
    • container_titlestring
    • doistring
    • issnstring[]
    • issuestring | null
    • languagestring
    • open_accessobject
      • is_oaboolean
      • statusstring
      • urlnull | string
    • pagestring
    • publishedstring
    • publisherstring
    • titlestring
    • typestring
    • urlstring
    • volumestring
    • work_idstring
    • yearinteger
  • next_pageinteger
  • pageinteger
  • querynull
  • sortstring
  • totalinteger

Loading related APIs…

Common questions

Do I need a separate key for every provider?

Use your OpenAny API key for standard API access. Read it from OPENANY_API_KEY in your environment and keep it out of prompts, source code and logs.

Are these providers interchangeable?

No. Each offering has its own inputs, pricing and response contract. Selecting a catalog offering does not establish automatic routing or fallback. Confirm the service contract before calling.

How is this API billed?

API-key calls use your shared balance at the selected implementation's published rate. Check the billing unit and request-specific pricing rules before making a paid call. Recorded usage determines the final charge under that contract.

Where do the price and contract come from?

The selected implementation publishes its provider, request contract, revision and billing rules through OpenAny's public API catalog. A revision number identifies a contract version, not a price update date. A price update timestamp is not supplied; do not treat a page date as one.

How do OpenAny Balance and x402 differ?

OpenAny Balance uses an API key and one shared balance. Card, USDC and x402 top-ups, card auto top-up and USDC subscriptions fund that balance; available routes appear on the Credits page. Direct x402 is a separate pay-per-request flow, available only on listings that show it and requiring an authorized payment client.

Does Playground send a paid request?

Yes. After you sign in, Run sends a real API request using an active OpenAny API key. Charges follow the published API contract and use your shared balance. Selecting an implementation, editing inputs and viewing sample responses do not send requests.

Use Research Papers citing works API with your agent

Inspect endpoint contracts and confirm availability and pricing before a paid call.