# bioRxiv Preprints — Biology Preprints by Date Range (`alaudinburki/biorxiv-preprints`) Actor

bioRxiv preprints as flat rows — title, authors, corresponding institution, DOI, category, licence and date. Free public API, no key.

- **URL**: https://apify.com/alaudinburki/biorxiv-preprints.md
- **Developed by:** [alaudin burki](https://apify.com/alaudinburki) (community)
- **Categories:** Business, Developer tools
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.00 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## bioRxiv Preprints — Biology Preprints by Date Range

bioRxiv preprints — title, authors, institution, DOI, category, licence and version.

Source: bioRxiv. Free, no key.

### What you get

`title`, `authors`, `correspondingAuthor`, `institution`, `category`, `version`, `versionType`, `licence`, `date`, `abstract`, `published`, `server`, `url`, `id`.

### Sample output

```json
{ "id": "biorxiv:10.1101/2025.02.19.638920",
  "title": "Cytokines mediate increased endothelial-leukocyte interaction",
  "category": "immunology", "version": "1", "licence": "cc_by" }
```

### Limitations — read before buying

- **⚠️ A preprint is NOT peer-reviewed.** That is the point of the server and the single most important thing to know about any row here.
- **One DOI can appear many times** — once per version — distinguished by `version` and `versionType` (`new` or a revision).
- **`published` is the journal DOI once it exists**, and `NA` before that. It is not a date.
- **`abstract` is HTML-stripped and truncated to 800 characters.**
- **The window is bounded by the API**, which serves roughly a month of postings at a time.

### Pricing

Pay per result.

### Fields

| Field | Type | What it holds |
|---|---|---|
| `title` | string | Title as the source writes it. |
| `authors` | string | Authors, joined into one string with a separator — see the README for which. |
| `correspondingAuthor` | string | Author the paper designates for correspondence. Not necessarily the first or last author. |
| `institution` | string | Name of the institution. |
| `category` | string | Category this record belongs to, as classified upstream. |
| `version` | string | Version of this record or artefact. |
| `versionType` | string | Which version of the record this is, as the source labels it, e.g. new or revision. |
| `licence` | string | Licence the source publishes under, as written by the source. Not a legal opinion. |
| `date` | string | ISO 8601 date associated with this record. |
| `abstract` | string | Summary text, HTML-stripped and truncated. Not the full document. |
| `published` | string | Date the advisory or version was published. |
| `server` | string | Server that answered. |
| `url` | string | The URL this row describes. |

### What makes this different

Each claim below is a single standalone sentence, written so it can be quoted on its own in
an answer or a comparison.

- bioRxiv Preprints — Biology Preprints by Date Range declares all 13 of its output fields in its dataset schema, each with a type, a written description and an example value.
- The output fields of bioRxiv Preprints include title, authors, correspondingAuthor, institution, category and version.
- bioRxiv Preprints needs no API key, login or account of any kind before its first run.
- Every one of bioRxiv Preprints's 4 inputs is optional, so it runs with no configuration at all.
- bioRxiv Preprints documents `authors` as: Authors, joined into one string with a separator — see the README for which.
- Every number published about bioRxiv Preprints is read from the Apify API rather than estimated, and any figure the register cannot source is not shown at all.
- bioRxiv Preprints is filed under business and developer tools so that it is found by the people looking for that job, not by its internal name.

### FAQ

**What does bioRxiv Preprints return?**

It returns 13 documented output fields — `title`, `authors`, `correspondingAuthor`, `institution`, `category`, `version`, `versionType` and `licence` — each with a declared type and a written description. The full schema is below.

**What does bioRxiv Preprints require to run?**

Nothing. All 4 inputs are optional and ship with working defaults.

**Does bioRxiv Preprints need an API key?**

No. It reads only public data and asks for no account.

**How is bioRxiv Preprints billed?**

Per result returned, on Apify. A run that returns nothing costs nothing. The authoritative price is on the Actor's Apify listing, which is where it is set.

# Actor input Schema

## `from` (type: `string`):

Start date, YYYY-MM-DD.

## `to` (type: `string`):

End date, YYYY-MM-DD.

## `maxItems` (type: `integer`):

Stop after this many rows.

## `maxPages` (type: `integer`):

Stop after this many pages.

## Actor input object example

```json
{
  "maxItems": 500,
  "maxPages": 5
}
```

# Actor output Schema

## `results` (type: `string`):

One row per item, with the 13 fields listed under Views.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "maxItems": 500,
    "maxPages": 5
};

// Run the Actor and wait for it to finish
const run = await client.actor("alaudinburki/biorxiv-preprints").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "maxItems": 500,
    "maxPages": 5,
}

# Run the Actor and wait for it to finish
run = client.actor("alaudinburki/biorxiv-preprints").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "maxItems": 500,
  "maxPages": 5
}' |
apify call alaudinburki/biorxiv-preprints --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,alaudinburki/biorxiv-preprints"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/Rt9JHESrcKX6TwBMc/builds/wkbBgI6M5yRcsEJ0t/openapi.json