Automate WikiPathways Webservices
HumDay reads WikiPathways Webservices’s own published API description and derives 27 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.
What HumDay can do in WikiPathways Webservices
1 documented operations change something in WikiPathways Webservices.
- POSTcreatePathwayCreate a new pathway on the wiki with the given GPML code.
/createPathway
What HumDay can read from WikiPathways Webservices
These are the operations a schedule or a trigger can watch.
- GETloginStart a logged in session, using an existing WikiPathways account.
/login - GETgetPathwayAsDownload a pathway in the specified file format.
/getPathwayAs - GETlistPathways
/listPathways - GETlistOrganisms
/listOrganisms - GETupdatePathwayUpdate a pathway on the wiki with the given GPML code.
/updatePathway - GETgetUserByOrcid
/getUserByOrcid - GETsaveOntologyTag
/saveOntologyTag - GETfindInteractionsFind interactions defined in WikiPathways pathways.
/findInteractions - GETremoveOntologyTag
/removeOntologyTag - GETfindPathwaysByLiterature
/findPathwaysByLiterature - GETgetPathwaysByOntologyTerm
/getPathwaysByOntologyTerm - GETgetPathwaysByParentOntologyTerm
/getPathwaysByParentOntologyTerm - GETgetPathway
/getPathway - GETgetXrefList
/getXrefList - GETgetPathwayInfoGet some general info about the pathway, such as the name, species, without downloading the GPML.
/getPathwayInfo - GETgetCurationTagsGet all curation tags for the given tag name.
/getCurationTags - GETsaveCurationTag
/saveCurationTag - GETgetRecentChangesGet the recently changed pathways.
/getRecentChanges - GETgetColoredPathwayGet a colored image version of the pathway.
/getColoredPathway - GETgetPathwayHistoryGet the revision history of a pathway.
/getPathwayHistory - GETremoveCurationTagRemove a curation tag from a pathway.
/removeCurationTag - GETfindPathwaysByText
/findPathwaysByText - GETfindPathwaysByXref
/findPathwaysByXref - GETgetCurationTagHistory
/getCurationTagHistory - GETgetCurationTagsByNameGet all curation tags for the given tag name.
/getCurationTagsByName - GETgetOntologyTermsByPathway
/getOntologyTermsByPathway
How automating WikiPathways Webservices works
- Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
- Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
- See it proven. The program runs and shows you the result before it is allowed near your live WikiPathways Webservices account.
- Grant access, then go live. You approve the specific WikiPathways Webservices operations it may use — and only those.
Questions about WikiPathways Webservices automation
- Can HumDay connect to WikiPathways Webservices?
- Yes. HumDay reads WikiPathways Webservices's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 27 operations are documented.
- Do I need to write code to automate WikiPathways Webservices?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your WikiPathways Webservices account.
- What can HumDay do in WikiPathways Webservices?
- 1 of the 27 documented operations change something in WikiPathways Webservices, and 26 read from it. HumDay only ever uses the specific operations your approved contract needs.
- Is my WikiPathways Webservices account safe?
- Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to WikiPathways Webservices is held behind that approval.
Where this came from
The operations above are read from a published API description for WikiPathways Webservices at webservice.wikipathways.org/index.php?swagger. Descriptions are the provider’s own words, not ours. Last published 2021-06-21.