Can HumDay connect to Monarchinitiative BioLink?

Yes. HumDay reads Monarchinitiative BioLink's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 164 operations are documented.

Do I need to write code to automate Monarchinitiative BioLink?

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 Monarchinitiative BioLink account.

What can HumDay do in Monarchinitiative BioLink?

14 of the 164 documented operations change something in Monarchinitiative BioLink, and 150 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my Monarchinitiative BioLink 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 Monarchinitiative BioLink is held behind that approval.

Automate Monarchinitiative BioLink

HumDay reads Monarchinitiative BioLink’s own published API description and derives 164 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 Monarchinitiative BioLink is

API integration layer for linked biological objects. __Source:__ https://github.com/biolink/biolink-api/

What HumDay can do in Monarchinitiative BioLink

14 documented operations change something in Monarchinitiative BioLink.

POSTCreates a new variant set/variation/set/
POSTMatch a patient to fruit fly genes based on similar phenotypes/mme/fly
POSTMatch a patient to mouse genes based on similar phenotypes/mme/mouse
POSTGet annotation score/sim/score
POSTMatch a patient to diseases based on their phenotypes/mme/disease
POSTCompare a reference profile vs one or more profiles/sim/compare
POSTMatch a patient to nematode genes based on similar phenotypes/mme/nematode
POSTMatch a patient to zebrafish genes based on similar phenotypes/mme/zebrafish
POSTAnnotate a given text using SciGraph annotator/nlp/annotate/
POSTFetches a map from CURIEs/IDs to labels/ontol/identifier/
POSTAnnotate a given content using SciGraph annotator and get all entities from content/nlp/annotate/entities
DELETEDeletes variant set/variation/set/{id}
PUTUpdates a variant set/variation/set/{id}
POSTExtract a subgraph from an ontology/ontol/subgraph/{ontology}/{node}

What HumDay can read from Monarchinitiative BioLink

These are the operations a schedule or a trigger can watch.

GETReturns list of models matching query/cam/model/query
GETReturns list of matching concepts or entities using lexical search/search/entity/{term}
GETReturns list of ALL models/cam/model
GETSearch for phenotypically similar diseases or model genes/sim/search
GETReturns list of models/cam/activity
GETReturns list of all instances/cam/instances
GETReturns list of variant sets/variation/set/
GETReturns list of prefixes/identifier/prefixes/
GETReturns list of matching concepts or entities using lexical search/search/entity/hpo-pl/{term}
GETReturns list of models/cam/physical_interaction
GETReturns list of matching concepts or entities using lexical search/search/entity/autocomplete/{term}
GETReturns list of matches/individual/{id}
GETReturns list of all properties used across all models/cam/model/properties
GETReturns list of all contributors across all models/cam/model/contributors
GETReturns list property-values for all models/cam/model/property_values
GETReturns list of matches/cam/instance/{id}
GETReturns list of matching associations pointing to a given object (target)/association/to/{object}
GETReturns list of matches/individual/pedigree/{id}
GETReturns list of matching associations starting from a given subject (source)/association/from/{subject}
GETGet annotation score/sim/score
GETReturns list of matching associations for a given subject category/association/find/{subject_category}
GETReturns list of matching associations of a given type/association/type/{association_type}
GETCompare a reference profile vs one profiles/sim/compare
GETAnnotate a given text using SciGraph annotator/nlp/annotate/
GETFetches a map from CURIEs/IDs to labels/ontol/labeler/
GETAll relations used plus count of associations/relation/usage/
GETGet metadata for all datasets from SciGraph/metadata/datasets
GETFetches a map from CURIEs/IDs to labels/ontol/identifier/
GETTODO Graph object spanning all entities/bioentityset/graph
GETReturns list of matches/variation/set/analyze/{id}
GETReturns homology associations for a given input set of genes/bioentityset/homologs/
GETPlaceholder - use direct SPARQL endpoint for now/owl/ontology/sparql/{query}
GETPlaceholder - use OWLery for now/owl/ontology/dlquery/{query}
GETReturns compact associations for a given input set/bioentityset/associations
GETReturns basic info on object of any type/bioentity/{id}
GETReturns the association with a given identifier/association/{id}
GETSummary statistics for objects associated/bioentityset/overrepresentation
GETRelation usage count for all subj x obj category combinations/relation/usage/pivot
GETAnnotate a given content using SciGraph annotator and get all entities from content/nlp/annotate/entities
GETTODO maps a list of identifiers from a source to a target/identifier/mapper/{source}/{target}/
GETFor a given gene(s), summarize its annotations over a defined set of slim/bioentityset/slimmer/anatomy
GETFor a given gene(s), summarize its annotations over a defined set of slim/bioentityset/slimmer/function
GETReturns a complete model/cam/model/{id}
GETSummary statistics for objects associated/bioentityset/descriptor/counts
GETFor a given gene(s), summarize its annotations over a defined set of slim/bioentityset/slimmer/phenotype
GETReturns a graph node/graph/node/{id}
GETReturns expression events for a gene/bioentity/gene/{id}/expression/anatomy
GETReturns meta data of an ontology term/ontology/term/{id}
GETReturns a variant set/variation/set/{id}
GETReturns evidence graph object for a given association/evidence/graph/{id}
GETReturns meta data of an ontology subset (slim)/ontology/subset/{id}
GETReturns annotations associated to a function term/bioentity/function/{id}
GETReturns associations for an entity regardless of the type/bioentity/{id}/associations
GETReturns list of matching associations between a given subject and object category/association/find/{subject_category}/{object_category}
GETRelation usage count for all subj x obj category combinations, showing label/relation/usage/pivot/label
GETReturn basic info on an object for a given type/bioentity/{type}/{id}
GETReturns edges emanating from a given node/graph/edges/from/{id}
GETReturns graph of an ontology term/ontology/term/{id}/graph
GETReturns cases associated with a gene/bioentity/gene/{id}/cases
GETReturns evidence as a associationresults object given an association/evidence/graph/{id}/table
GETReturns models associated with a case/bioentity/case/{id}/models
GETReturns models associated with a gene/bioentity/gene/{id}/models
GETReturns cases associated with a model/bioentity/model/{id}/cases
GETReturns genes associated with a model/bioentity/model/{id}/genes
GETReturns subsets (slims) associated to an ontology term/ontology/term/{id}/subsets
GETReturns anatomical entities associated with a gene/bioentity/gene/{id}/anatomy
GETExtract a subgraph from an ontology term/ontology/term/{id}/subgraph
GETReturns genes associated with a given anatomy/bioentity/anatomy/{id}/genes
GETReturns diseases associated with a case/bioentity/case/{id}/diseases
GETReturns variants associated with a case/bioentity/case/{id}/variants
GETReturns cases associated with a disease/bioentity/disease/{id}/cases
GETReturns genes associated with a disease/bioentity/disease/{id}/genes
GETReturns diseases associated with gene/bioentity/gene/{id}/diseases
GETReturns function associations for a gene/bioentity/gene/{id}/function
GETReturns homologs for a gene/bioentity/gene/{id}/homologs
GETReturns pathways associated with gene/bioentity/gene/{id}/pathways
GETReturns variants associated with a gene/bioentity/gene/{id}/variants
GETReturns genes associated with a pathway/bioentity/pathway/{id}/genes
GETReturns cases associated with a variant/bioentity/variant/{id}/cases
GETReturns genes associated with a variant/bioentity/variant/{id}/genes
GETReturns genotypes associated with a case/bioentity/case/{id}/genotypes
GETReturns associations to models of the disease/bioentity/disease/{id}/models
GETReturns genes associated to a GO term/bioentity/function/{id}/genes
GETReturns genotypes associated with a gene/bioentity/gene/{id}/genotypes
GETReturns cases associated with a genotype/bioentity/genotype/{id}/cases
GETReturns genes associated with a genotype/bioentity/genotype/{id}/genes

How automating Monarchinitiative BioLink 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 Monarchinitiative BioLink account.
Grant access, then go live. You approve the specific Monarchinitiative BioLink operations it may use — and only those.