Demos how to query the Graph Network Arbitrum Subgraph published to The Graph Network using an API Key obtained on The Graph Studio in a NextJS
application using the nextjs pages router.
A key component to this example is that queries to the Subgraph are routed through the nextjs api. This helps with a specific use-case of helping to secure your API Key; either through the client-side JavaScript shipped to the browser, or through network requests. This is a good way to build a dapp that queries a Subgraph that secures your API Key to prevent leaks. The downside to this approach is that each request makes two HTTP requests:
- from the nextjs app client/ssr to the nextjs api that queries the Subgraph
- from the nextjs api to the Subgraph.
This is an important consideration when building a dapp that queries the Subgraph.
# Clone Repo
git clone [email protected]:graphprotocol/query-examples.git
# CD into nextjs-pages-router example
cd ./examples/nextjs-pages-router
# Install bun package manager, if needed
curl -fsSL https://bun.sh/install | bash
# Install deps
bun install
# Run
bun run dev
This app exposes a GraphQL API at /api/graphql
, defined in the /pages/api/graphql.ts
file. It fields GET
and POST
requests and accepts a graphql request. It then sends the request to the Subgraph and returns the response after querying the Subgraph on The Graph Network using your API Key.
This is how you secure your API Key from leaks by routing requests through the next api server.
# Copy the example env file into a .env
cp ./.env.example ./.env
# replace the `{your api key here}` with your API Key
API_KEY
- the 32-digit API Key created in The Graph Studio.- Note in this example, the env var is exposed to the client.
ROOT_URI
- the url the app is running on. used to query the graphql api exposed by the app to route requests to the subgraph through.- default: http://localhost:3000/api/graphql
This repo utilizes graphql codegen. This validates our graphql and generates types to match the queries written for the app. These types can then be used to make our components type-safe to the graphql queries that will hydrate them.
# have to run the app
bun run dev
# run graphql codegen to regen types from updated queries
bun run codegen.gql