Important: WikiPathways Technical Transition - Action Required for Some Users

Dear WikiPathways Community,

Effective April 1st, 2026, we will begin taking major steps toward retiring the classic WikiPathways backend as we complete our migration to our GitHub-based infrastructure.

1/

#wikipathways #biology #openscience

Over the past few years, we've undergone significant technical developments, with the migration from our classic database to a GitHub-based setup being the most substantial. We've maintained both systems in parallel with daily synchronization to ensure a smooth transition, but it's now time to complete this move. 2/

What This Means for You

For Users: Nothing changes! You can continue to find all pathways on our website (www.wikipathways.org), download pathways, use them for your analyses, and explore the content exactly as you always have.

3/

For Curators: During this transition period, submitting new pathways may require a bit more effort than you're accustomed to, and the process may not be as streamlined as before. We understand this may cause some inconvenience, but please don't hesitate to contact us! We are ready and eager to support you through the submission process and any challenges you encounter.

4/

For Developers: This is critical - if you are still using the old REST webservice (https://webservice.wikipathways.org/), you need to take action now!

- The new JSON API (https://www.wikipathways.org/json/) has been available for over a year

- Key tools have already been updated: rWikiPathways, the Cytoscape app, and our release tools all work with the new infrastructure

- Action required: If you haven't switched to the new API yet, please reach out to us immediately

5/

Swagger UI

Whether you're a curator preparing pathway submissions or a developer migrating your tools, we're here to support you. Don't wait - reach out now so we can ensure a smooth transition.

https://github.com/wikipathways/wikipathways-help/discussions/223

6/6