bioRxiv alerts let researchers and developers track newly posted preprints in a chosen subject area without manually rechecking the site — the three core options are subject-category email alerts, per-category RSS/Atom feeds, and the public bioRxiv API, each suited to a different workflow. bioRxiv is the preprint server for biology operated by openRxiv, a nonprofit dedicated to advancing scientific communication, and it exposes the same underlying content through all three channels plus social feeds on Bluesky, Mastodon and X.
This guide compares the four practical ways to follow new bioRxiv postings — email alerts, RSS/Atom feeds, the REST API, and social feeds — so you can pick the right combination for a literature-monitoring workflow, a lab dashboard, or an automated pipeline.
- What are bioRxiv’s alert options?
- How do bioRxiv email alerts work?
- How do bioRxiv RSS feeds work?
- What can the bioRxiv API do that alerts can’t?
- Should you follow bioRxiv on Bluesky, Mastodon or X?
- Which option should you choose?
- Common questions about bioRxiv alerts
What are bioRxiv’s alert options?
bioRxiv is a preprint server for the biological sciences; a preprint is a complete scientific manuscript posted online before, or without, formal peer review. Because thousands of preprints are posted every week across dozens of subject categories, bioRxiv publishes the same feed of new content through four distinct channels rather than a single notification system.
Each channel trades off timeliness, filtering precision and technical effort differently. Email alerts and RSS feeds are built for passive monitoring by individual researchers; the API is built for developers who need structured metadata inside another tool; social feeds suit anyone already working inside those platforms.
How do bioRxiv email alerts work?
Email alerts are the lowest-effort option for an individual researcher who wants a periodic digest. You sign up on the bioRxiv Alerts page, select one or more of bioRxiv’s roughly 30 subject categories — from Bioinformatics to Zoology — and bioRxiv emails you when matching preprints are posted.
- Alerts can be scoped to a subject category, a keyword search, or a specific author.
- You can add or remove subject-area alerts at any time from the same sign-up page, without deleting your account.
- No bioRxiv account or login is required simply to receive category alerts — the sign-up form only asks for an email address.
This makes email alerts the right default for anyone who wants new preprints in their inbox without building or maintaining anything.
How do bioRxiv RSS feeds work?
bioRxiv’s Alerts/RSS page publishes an Atom 1.0 feed for each subject category, plus a combined feed across all categories. Each feed returns only the most recent 30 posts for that category — a hard limit set by bioRxiv, not a filter you can extend — so an RSS reader that checks infrequently can silently miss older items once more than 30 new preprints accumulate.
Feeds can be combined by chaining subject categories with a plus sign in the URL, and multi-word category names use an underscore in place of a space. For example, a feed combining Genomics and Bioinformatics takes the form:
http://connect.biorxiv.org/biorxiv_xml.php?subject=genomics+bioinformatics
This lets a single feed reader subscription cover several adjacent subject areas — useful for interdisciplinary groups — without needing separate subscriptions per category.
What can the bioRxiv API do that alerts and RSS can’t?
The bioRxiv API is a pull-based REST interface returning structured JSON metadata — DOI, title, authors, category, posting date and abstract — for preprints on bioRxiv and medRxiv. Unlike email alerts or RSS, it has no built-in subject-category filter parameter and no push/webhook mechanism: a developer must query by date interval or DOI and filter the returned category field client-side.
That distinction matters for anyone building automated tooling:
- The API suits scheduled polling jobs, institutional repository harvesters, and research-tool dashboards that need structured metadata, not just a headline and link.
- RSS and email alerts remain the simpler choice for a single researcher who only wants to read new titles as they appear.
- Because the API is pull-based, any “alert” built on top of it requires you to run your own polling schedule and de-duplication logic.
Detailed field definitions and endpoint syntax are published in bioRxiv’s own API documentation, which developers should consult directly before building a production integration.
Should you follow bioRxiv on Bluesky, Mastodon or X?
bioRxiv also mirrors new postings to social platforms, and this is where the biggest recent change sits — one that generic alert guides tend to miss. Beyond the long-standing X/Twitter account (@biorxivpreprint, over 140,000 followers, plus a dedicated account per subject category), bioRxiv now runs an equivalent set of per-category streams on Bluesky (e.g. biorxiv-bioinfo.bsky.social) and Mastodon (e.g. biorxiv_bioinfo on biologists.social).
This matters because X restricted free API access in 2023, which reduced the reliability of X-based bots and dashboards that many labs had built to watch subject feeds. Bluesky and Mastodon’s open, API-friendly protocols make them a more dependable base for anyone building a custom preprint-monitoring bot today, rather than a nice-to-have alternative.
Which option should you choose?
The right channel depends on how much filtering precision you need and how much technical effort you are willing to invest.
| Channel | Best for | Filtering | Setup effort | Key limitation |
|---|---|---|---|---|
| Email alerts | Individual researchers wanting a digest | Subject, keyword, author | None (email only) | No login needed, but digest cadence isn’t real time |
| RSS/Atom feed | Feed-reader users, interdisciplinary groups | Subject category, combinable | Low (add feed URL) | Capped at the most recent 30 posts per category |
| REST API | Developers, institutional tools, dashboards | None built-in; filter client-side | High (build a polling job) | Pull-based only, no webhook/push |
| Bluesky/Mastodon/X | Social monitoring, bot-building | Per subject-category account | Low–Medium | X reach reduced since 2023 API restrictions |
For most individual researchers, subject-category email alerts remain the simplest reliable option. Developers building institutional or lab-wide monitoring tools should combine the API for structured metadata with RSS as a lightweight fallback.
Common questions about bioRxiv alerts
Why are my bioRxiv email alerts not working?
Missed bioRxiv alerts are usually caused by an out-of-date subject-category selection, an alert email landing in a spam or promotions folder, or an expired confirmation link. Re-visiting the bioRxiv Alerts page and re-confirming your chosen categories resolves most cases.
Do I need a bioRxiv account or login to set up alerts?
No account or login is required for basic email alerts — only an email address. A bioRxiv account is only needed for actions like submitting a manuscript, posting a comment, or managing an author profile, not for receiving subject-area notifications.
Does bioRxiv have a public API for developers?
Yes. bioRxiv publishes a public REST API returning JSON metadata — including DOI, title, category and abstract — for content on bioRxiv and medRxiv. It is pull-based, so developers must schedule their own queries rather than receive push notifications.
Should I track bioRxiv or arXiv for my subject area?
Choose based on discipline, not preference: bioRxiv covers biology-specific subject categories, while arXiv covers physics, mathematics, computer science and quantitative biology. Researchers working across both fields — for example in computational biology — often need alerts from both servers rather than treating them as interchangeable.
What this means for research-monitoring workflows
Preprint volume keeps growing across biology subject categories, and no single channel covers every use case. A researcher who only needs a daily digest is well served by email alerts; a developer building a literature-surveillance tool for an institution needs the API’s structured metadata and should plan for its pull-based, polling architecture from the outset. Teams that previously relied solely on X-based bots should treat the 2023 API restrictions as a prompt to add Bluesky or Mastodon, or the official RSS feed, as a more durable foundation.
Research administrators supporting open-scholarship workflows can pair these tracking methods with broader terminology in the CASRAI Dictionary when documenting how preprints fit into an institution’s research-administration processes.
Leave a Reply