Skip to content

Create an account and get up to 25% off.

Order

Pathway Mouse Mus musculus

Read this first

Every mouse pathway in Reactome is electronically inferred from the curated human one; Reactome's own sentence about that stands beside the record below.

Class B/2 (Secretin family receptors)

R-MMU-373080 in Reactome release 97: under GPCR ligand binding, with 58 genes placed in it by the mapping files and 2 child pathways in the hierarchy.

The same number in the other species

Reactome writes the mouse and rat events it infers from a human pathway under the human number with the species token. A door opens only where that species' own list in this release holds the id: R-HSA-373080 (human), R-RNO-373080 (rat). Whether the event was inferred from this one is what the record says.

01The record

Reactome's own record of this pathway

What this tells you

The pathway list, the hierarchy and the genes on this page are read from the files Reactome publishes for Reactome release 97, built into this site on 2026-09-09: the pathway list, the hierarchy relationship file and the two gene mapping files. The record card is the one live read, Reactome's own record of this pathway.

Reactome's download page describes the mapping files: Mapping files link the source database identifier to the lowest level pathway diagram or subset of the pathway, all levels of the pathway hierarchy or database identifier to all reactions. [R13] The gene list here is the all-levels mapping of NCBI Gene ids, filled from the all-levels mapping of Ensembl ids where the NCBI file has no row for a gene; each row names which file it came from by the shape of its source id. Each row carries the evidence codes the file writes for it, as written and unranked, and both where the file writes both; no page of Reactome's documentation the survey read defines the codes, so this page does not expand them. A gene id the identity files do not name is kept as the source's own id with no door rather than turned into a symbol.

Every mouse pathway in Reactome is inferred from the curated human one: We use the set of manually curated human reactions to electronically infer reactions in fourteen evolutionarily divergent eukaryotic species for which high-quality whole-genome sequence data are available, and hence a comprehensive and high-quality set of protein predictions exists. [R11] Reactome's own sentence about what that produces is printed beside the record: The electronically inferred reactions presented in Reactome are thus not data, but hypotheses useful to direct the design of confirmatory experiments. [R11]

On citing what a search finds, Reactome says: It should be remembered that while we strive to contain the most current and accurate data, Reactome should not be used in citations where other primary sources of information are available. [R12] The record card prints the literature Reactome attaches to a curated pathway for that reason. The data are public domain: All data in the Reactome database and files derived from that data are licensed under the Creative Commons Public Domain Dedication (CC0). User may copy, modify, and distribute these data, even for commercial purposes, without asking for permission. Attribution is encouraged but not required. [R10] The pathway illustrations are licensed apart, under CC BY 4.0, and none is shown here.

A gene on this list is one Reactome places in this pathway in this release, and that is all the row says: it does not say the gene is expressed in a tissue or associated with a disease, which are the other two explorers' questions, read from other sources. Reactome's papers of record are [R01] [R02].

  1. [R01] Ragueneau E, Gong C, Sinquin P, Sevilla C, Beavers D, Grentner A, et al. (2026). The Reactome Knowledgebase 2026. Nucleic Acids Research 54:D673-D681. PMID 41251150, doi 10.1093/nar/gkaf1223.
  2. [R02] Milacic M, Beavers D, Conley P, Gong C, Gillespie M, Griss J, et al. (2024). The Reactome Pathway Knowledgebase 2024. Nucleic Acids Research 52:D672-D678. PMID 37941124, doi 10.1093/nar/gkad1025.
  3. [R10] Reactome, reactome.org. License Agreement. https://reactome.org/license, read 2026-09-09.
  4. [R11] Reactome, reactome.org. Computationally inferred events. https://reactome.org/documentation/inferred-events, read 2026-09-09.
  5. [R12] Reactome, reactome.org. Citing us. https://reactome.org/cite, read 2026-09-09.
  6. [R13] Reactome, reactome.org. Download. https://reactome.org/download-data, read 2026-09-09.
Reading this pathway's record from Reactome (the pathway record).Still reading. A first read of a pathway can take a while; this page waits up to 35 seconds for it, and its scripts then bring in the panel, or a line saying what did not arrive.

02The genes

Genes Reactome places in this mouse pathway

The mapping files place 58 genes in this mouse pathway; showing 1 to 58, in pages of 100, sorted by symbol for reading. The order carries no ranking.

Genes Reactome places in this mouse pathway, page 1 of 1
GeneAdcyap1Authority11516Mapping file id11516 NCBI fileEvidenceIEA
GeneAdcyap1r1Authority11517Mapping file id11517 NCBI fileEvidenceIEA
GeneAdgre1Authority13733Mapping file id13733 NCBI fileEvidenceIEA
GeneAdgre5Authority26364Mapping file id26364 NCBI fileEvidenceIEA
GeneAdmAuthority11535Mapping file id11535 NCBI fileEvidenceIEA
GeneAdm2Authority223780Mapping file id223780 NCBI fileEvidenceIEA
GeneCalcaAuthority12310Mapping file id12310 NCBI fileEvidenceIEA
GeneCalcbAuthority116903Mapping file idENSMUSG00000030666 Ensembl fileEvidenceIEA
GeneCalcrAuthority12311Mapping file id12311 NCBI fileEvidenceIEA
GeneCalcrlAuthority54598Mapping file id54598 NCBI fileEvidenceIEA
GeneCd55Authority13136Mapping file id13136 NCBI fileEvidenceIEA
GeneCrhAuthority12918Mapping file id12918 NCBI fileEvidenceIEA
GeneCrhbpAuthority12919Mapping file id12919 NCBI fileEvidenceIEA
GeneCrhr1Authority12921Mapping file id12921 NCBI fileEvidenceIEA
GeneCrhr2Authority12922Mapping file id12922 NCBI fileEvidenceIEA
GeneGcgAuthority14526Mapping file id14526 NCBI fileEvidenceIEA
GeneGcgrAuthority14527Mapping file id14527 NCBI fileEvidenceIEA
GeneGhrhAuthority14601Mapping file id14601 NCBI fileEvidenceIEA
GeneGhrhrAuthority14602Mapping file id14602 NCBI fileEvidenceIEA
GeneGipAuthority14607Mapping file id14607 NCBI fileEvidenceIEA
GeneGiprAuthority381853Mapping file id381853 NCBI fileEvidenceIEA
GeneGlp1rAuthority14652Mapping file id14652 NCBI fileEvidenceIEA
GeneGlp2rAuthority93896Mapping file id93896 NCBI fileEvidenceIEA
GeneGnasAuthority14683Mapping file id14683 NCBI fileEvidenceIEA
GeneGnb1Authority14688Mapping file id14688 NCBI fileEvidenceIEA
GeneGnb2Authority14693Mapping file id14693 NCBI fileEvidenceIEA
GeneGnb3Authority14695Mapping file id14695 NCBI fileEvidenceIEA
GeneGnb4Authority14696Mapping file id14696 NCBI fileEvidenceIEA
GeneGnb5Authority14697Mapping file id14697 NCBI fileEvidenceIEA
GeneGng10Authority14700Mapping file id14700 NCBI fileEvidenceIEA
GeneGng11Authority66066Mapping file id66066 NCBI fileEvidenceIEA
GeneGng12Authority14701Mapping file id14701 NCBI fileEvidenceIEA
GeneGng13Authority64337Mapping file id64337 NCBI fileEvidenceIEA
GeneGng2Authority14702Mapping file id14702 NCBI fileEvidenceIEA
GeneGng3Authority14704Mapping file id14704 NCBI fileEvidenceIEA
GeneGng4Authority14706Mapping file id14706 NCBI fileEvidenceIEA
GeneGng5Authority14707Mapping file id14707 NCBI fileEvidenceIEA
GeneGng7Authority14708Mapping file id14708 NCBI fileEvidenceIEA
GeneGng8Authority14709Mapping file id14709 NCBI fileEvidenceIEA
GeneGngt1Authority14699Mapping file id14699 NCBI fileEvidenceIEA
GeneGngt2Authority14710Mapping file id14710 NCBI fileEvidenceIEA
GeneIappAuthority15874Mapping file id15874 NCBI fileEvidenceIEA
GenePthAuthority19226Mapping file id19226 NCBI fileEvidenceIEA
GenePth1rAuthority19228Mapping file id19228 NCBI fileEvidenceIEA
GenePth2Authority114640Mapping file id114640 NCBI fileEvidenceIEA
GenePth2rAuthority213527Mapping file id213527 NCBI fileEvidenceIEA
GenePthlhAuthority19227Mapping file idENSMUSG00000048776 Ensembl fileEvidenceIEA
GeneRamp1Authority51801Mapping file id51801 NCBI fileEvidenceIEA
GeneRamp2Authority54409Mapping file id54409 NCBI fileEvidenceIEA
GeneRamp3Authority56089Mapping file id56089 NCBI fileEvidenceIEA
GeneSctAuthority20287Mapping file id20287 NCBI fileEvidenceIEA
GeneSctrAuthority319229Mapping file id319229 NCBI fileEvidenceIEA
GeneUcnAuthority22226Mapping file id22226 NCBI fileEvidenceIEA
GeneUcn2Authority171530Mapping file id171530 NCBI fileEvidenceIEA
GeneUcn3Authority83428Mapping file id83428 NCBI fileEvidenceIEA
GeneVipAuthority22353Mapping file id22353 NCBI fileEvidenceIEA
GeneVipr1Authority22354Mapping file id22354 NCBI fileEvidenceIEA
GeneVipr2Authority22355Mapping file id22355 NCBI fileEvidenceIEA

Evidence codes on this page: IEA, as the mapping file writes them; a row carrying two was written twice by the file, once under each. The mapping file id says which file placed the gene: an NCBI Gene id from NCBI2Reactome_All_Levels.txt, an Ensembl gene id from Ensembl2Reactome_All_Levels.txt. The two files can disagree about a code, so a row's codes are the one file's view. Measured by this site's build over this release on 2026-09-09: the two files disagree on none of the 87,729 mouse pairs both place.

  • Reactome mapping files, the mouse rows for this pathway · Reactome release 97 · read · Reactome downloads"NCBI2Reactome_All_Levels.txt" and "Ensembl2Reactome_All_Levels.txt", Reactome, release 97, https://reactome.org/download-data/ (date of access 2026-09-09). Data CC0; attribution encouraged.

03The hierarchy

Parents and children in this release's hierarchy

Reactome's hierarchy is a graph rather than a tree: a pathway can sit under more than one parent, and the gene counts are each pathway's own placements at every level under it, so a parent's count is not the sum of its children's.

  • Reactome, the mouse pathway list and hierarchy relationship file · Reactome release 97 · read · Reactome downloads"ReactomePathways.txt" and "ReactomePathwaysRelation.txt", Reactome, release 97, https://reactome.org/download-data/ (date of access 2026-09-09). Data CC0; attribution encouraged.