# GraphQL API At Nomos we created our own backend to index data coming from the archway blockchain. Our system exposes a GraphQL API that you can use to get information about any multisig or proposal created. ### Endpoints by network * Archway mainnet (Triomphe): * Archway testnet (Constantine): For each of these endpoints, you need to request an access token for it. Go to our [discord](https://discord.com/invite/b7syPVx3S5) and connect with our team to get access to them. ### Usage You can use any GraphQL request tool you find useful, node-fetch, Axios, Apollo, etc. Just make sure to add the correct headers: * content-type: "application/json" * x-hasura-admin-secret: "\" ### Schema You can get more information about the schema objects and their relationships by connecting to our endpoint. * Account: Represents any account on the blockchain. * Contract: Represents any contract. * ContractInstance: Represents a contract deployed by a multisig. * ContractMetadata: Represents the metadata held by a contract. * Membership: Represents the relation between a multisig and a member of that multisig. * Multisig: A nomos multisignature wallet. * Proposal: A proposal created in a multisig. Can hold many messages. * Proposalmessage: A message in a proposal. Represents a message or a common transaction on the blockchain. * ProposalVotes: Represents a vote made in a proposal. * Transaction: Represents any transaction. Every action on the nomos contracts is related to a transaction. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://nomos-docs.gitbook.io/nomos-1/readme/protocol-overview/graphql-api.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.