Seeking Alternatives to GitHub GraphQL Explorer - What Tools Are You Using?

[azu]

Select Topic Area

Question

Body

GitHub is removing the GraphQL Explorer from API documentation on November 1, 2025.

• GraphQL Explorer removal from API documentation on November 1, 2025 - GitHub Changelog

What GraphQL tools are you using as alternatives?

I'm looking for recommendations for tools that can:

• Browse and test GitHub's GraphQL API
• Handle authentication with GitHub tokens
• Provide schema introspection and auto-completion

Additionally, I'd like to avoid Personal Access Tokens (PAT).
I'm looking for OAuth-based or other approaches that don't require storing a PAT.
(I used the official GraphQL Explorer because it did not require storing a PAT.)

Please share what you're using and how you set it up. Thanks!

[Argh94]

Hi! Thanks for asking about alternatives to GitHub’s GraphQL Explorer, which is being removed on November 1, 2025. Since you’re looking for tools to browse and test GitHub’s GraphQL API, handle authentication via OAuth (avoiding Personal Access Tokens), and provide schema introspection and auto-completion, I’ve put together a list of tools I’ve used or found effective, along with setup details. Here’s what I recommend:1. Apollo Studio ExplorerI’ve found Apollo Studio Explorer to be a fantastic replacement for GitHub’s GraphQL Explorer. It’s a powerful, web-based GraphQL IDE that checks all your boxes: it supports schema introspection, auto-completion, and OAuth-based authentication, so you don’t need to deal with PATs.Why I Like It: The interface is intuitive, similar to GitHub’s Explorer, and it lets me explore the schema, write queries with auto-completion, and save them for later. It’s perfect for interactive testing.
Setup Steps:Create a GitHub OAuth App:Go to GitHub Settings > Developer Settings > OAuth Apps > New OAuth App.
Set the callback URL (e.g., http://localhost:3000 for local testing or your app’s URL).
Save the Client ID and Client Secret.

Get an OAuth Token:Redirect users to:

https://github.com/login/oauth/authorize?client_id=YOUR_CLIENT_ID&scope=repo

After authorization, GitHub redirects to your callback URL with a code. Exchange it for an access token:

curl -X POST -d "client_id=YOUR_CLIENT_ID&client_secret=YOUR_CLIENT_SECRET&code=CODE" https://github.com/login/oauth/access_token

Store the token securely (no PAT needed).

Configure Apollo Studio:Visit Apollo Studio.
Set the endpoint to https://api.github.com/graphql.
Add a header: "Authorization": "Bearer YOUR_ACCESS_TOKEN".
Load the GitHub schema (download from GitHub Docs or use introspection). This enables auto-completion and schema browsing.

Testing Queries:Write queries in the Explorer with auto-completion (e.g., press Ctrl+Space).
Example query I use to check a repo:graphql

query { repository(owner: "octocat", name: "hello-world") { name stargazerCount } }

The Docs panel shows the schema, making it easy to explore fields.

Pros: Polished UI, robust OAuth support, and great for saving queries.
Cons: Setting up an OAuth app takes a few minutes, but it’s worth it to avoid PATs.
My Experience: I’ve used Apollo Studio for testing GitHub API queries, and the auto-completion saves me time when experimenting with complex queries like fetching pull requests or issues.

2. GraphiQLAnother tool I recommend is GraphiQL, an open-source GraphQL IDE that’s lightweight and flexible. It supports OAuth, schema introspection, and auto-completion, making it a solid alternative.Why I Like It: GraphiQL is simple to set up and works both as a standalone app or in-browser, which is great for quick testing without heavy dependencies.
   Setup Steps:Install GraphiQL:Download the standalone app from its GitHub repo or install via npm:

npm install -g graphiql

Alternatively, use the online version at graphiql-online.com.

Authenticate with OAuth:Follow the same OAuth setup as above to get an access token.
In GraphiQL, add a header in the HTTP Headers section:json

{ "Authorization": "Bearer YOUR_ACCESS_TOKEN" }

Set the Endpoint:Use https://api.github.com/graphql.

Load Schema:Run an introspection query to fetch the schema:graphql

query { __schema { types { name fields { name } } } }

This enables auto-completion and schema exploration in the Docs tab.

Test Queries:Write queries with auto-completion (e.g., Ctrl+Space).
Example I’ve tried:graphql

query { viewer { login repositories(first: 5) { nodes { name } } } }

Pros: Lightweight, open-source, and easy to use locally or online.
Cons: The UI is less polished than Apollo Studio, and you may need to manually load the schema.
My Experience: I’ve used GraphiQL for quick API tests when I didn’t want to set up a full IDE. It’s great for one-off queries and works well with OAuth.

3. GitHub CLI (gh)For terminal lovers like me, GitHub CLI (gh) is a surprisingly good option for running GraphQL queries without a graphical interface. It handles OAuth authentication automatically, so no PATs are needed, though it lacks built-in auto-completion.Why I Like It: It’s super convenient for scripting or quick API calls, and the OAuth flow is seamless since GitHub CLI manages tokens for you.
   Setup Steps:Install GitHub CLI:Install via Homebrew (macOS/Linux):

brew install gh

Or follow instructions at cli.github.com for other platforms.

Authenticate:Run:

gh auth login

Choose the browser-based OAuth flow. This authenticates you without needing a PAT.

Run GraphQL Queries:Use the gh api graphql command:bash

gh api graphql -f query='query { viewer { login name } }'

For schema introspection:bash

gh api graphql -f query='query { __schema { types { name fields { name } } } }' > schema.json

Filter results with --jq:bash

gh api graphql -f query='query { repository(owner:"octocat", name:"hello-world") { name } }' --jq '.data.repository.name'

Schema Exploration:Since there’s no built-in auto-completion, I pair it with GitHub’s public schema or use a text editor like VS Code with a GraphQL extension for auto-completion.

Pros: Zero PAT hassle, great for automation, and lightweight.
Cons: No graphical interface or built-in auto-completion, so it’s less interactive for schema exploration.
My Experience: I use GitHub CLI for automating GraphQL queries in scripts (e.g., fetching repo stats). It’s not ideal for interactive exploration but shines for quick, OAuth-based access.

4. GraphQL PlaygroundGraphQL Playground is another open-source IDE I’ve tried, similar to GraphiQL but with a slightly different interface. It supports OAuth, schema introspection, and auto-completion.Why I Like It: It’s a close match to GitHub’s Explorer in terms of functionality and works well for interactive query building.
   Setup Steps:Install GraphQL Playground:Download the desktop app from its GitHub repo or use the web version.

Authenticate with OAuth:Get an OAuth token using the same GitHub OAuth App process.
Add to HTTP Headers:json

{ "Authorization": "Bearer YOUR_ACCESS_TOKEN" }

Set Endpoint:Use https://api.github.com/graphql.

Load Schema:Run an introspection query or load the public schema to enable auto-completion.

Test Queries:Write queries with auto-completion and explore the schema in the DOCS tab.
Example:graphql

query { repository(owner: "octocat", name: "hello-world") { stargazerCount } }

Pros: User-friendly, supports OAuth, and open-source.
Cons: Less actively maintained than Apollo Studio or GraphiQL.
My Experience: I’ve used GraphQL Playground for smaller projects when I wanted a quick, browser-based IDE. It’s reliable but feels slightly dated compared to Apollo.

5. Postman (GraphQL Support)I’ve also used Postman for GraphQL queries since it added GraphQL support. It’s great if you’re already familiar with Postman for REST APIs and want OAuth-based authentication.Why I Like It: Postman’s OAuth 2.0 flow is straightforward, and it supports schema introspection and auto-completion, though it’s not as GraphQL-focused as Apollo.
   Setup Steps:Install Postman:Download from postman.com or use the web version.

Set Up OAuth 2.0:In Postman, create a new request, go to the “Authorization” tab, and select “OAuth 2.0”.
Enter your GitHub OAuth App’s Client ID, Client Secret, and authorization URL (https://github.com/login/oauth/authorize).
Postman handles the token exchange and stores it securely.

Configure GraphQL Request:Set the request to POST and the endpoint to https://api.github.com/graphql.
In the “Body” tab, select “GraphQL” and write your query.
Load the schema (via introspection or GitHub Docs) for auto-completion.

Test Queries:Example:graphql

query { viewer { login repositories(first: 5) { nodes { name } } } }

Pros: Familiar interface, strong OAuth support, and versatile for other APIs.
Cons: GraphQL features are newer and less polished than dedicated tools.
My Experience: I use Postman when I’m already working on REST APIs and want to test GraphQL queries in the same tool. It’s convenient but not my first choice for heavy GraphQL work.

My RecommendationAfter trying these tools, I’d recommend Apollo Studio Explorer as the closest match to GitHub’s GraphQL Explorer. It’s polished, supports OAuth seamlessly, and makes schema exploration and query building a breeze. If you prefer a terminal-based workflow, GitHub CLI is awesome for quick queries and automation, though you’ll need external tools for auto-completion.Extra TipsOAuth Workflow: Setting up an OAuth app takes a few minutes but ensures you avoid PATs. Always store tokens securely and refresh them as needed.
Schema Access: Download GitHub’s schema from GitHub Docs to use offline in tools like Apollo or GraphiQL.
Example Query: Here’s a query I often use to test OAuth setup:graphql

query GetRepoStars($owner: String!, $name: String!) {
repository(owner: $owner, name: $name) {
name
stargazerCount
}
}

Variables: {"owner": "octocat", "name": "hello-world"}

If you have a specific use case (e.g., automation vs. interactive testing) or need help with setup, let me know, and I can share more details or troubleshoot with you! Hope this helps!

[jihanurrahman33]

Hi @azu,

Here are solid alternatives to the soon-to-be-removed GraphQL Explorer, plus ways to avoid storing a long-lived PAT.

Good tool choices

• Altair GraphQL Client (desktop / browser extension)
  • Strong schema introspection, autocompletion, saved queries, envs.
• GraphiQL (desktop or self-hosted)
  • Lightweight, native Explorer feel; easy to point at api.github.com/graphql.
• Insomnia (GraphQL plugin) / Postman (GraphQL support)
  • Great for collections, envs, team sharing.
• VS Code + GraphQL extensions (e.g., GraphQL for VSCode)
  • Inline autocomplete/validation; run queries from editor.
• Apollo Sandbox/Studio Explorer
  • Superb schema UX; works via custom headers.

Endpoint for all of these: https://api.github.com/graphql

---

How to authenticate without a long-lived PAT

Option A — Use gh (GitHub CLI) as an auth broker (no PAT saved in the tool)

1. gh auth login (choose your account; device flow or browser).
2. For GUI tools that take a “Bearer token”, pass a short-lived token from gh:

   # One-liner to copy a token into your clipboard temporarily
   gh auth token

   Paste that into the tool’s Authorization: Bearer field.
   • Pros: You don’t create/store a PAT in the tool.
   • Tip: When you gh auth logout or rotate auth, the token changes.

Option B — OAuth App flow (user-based, no PAT)

• Create an OAuth App in Settings → Developer settings.
• Implement the standard code exchange to get a user access token, then use it in your client’s Authorization header (Bearer <token>).
• Many clients (Altair, Insomnia, Postman) support OAuth 2 callbacks so you don’t have to paste tokens manually.

Option C — GitHub App (installation access token; best for automation)

• Create a GitHub App, request needed read scopes, install it to your repos/org.
• Your backend exchanges a JWT for an installation access token and injects it as Authorization: Bearer.
• Tokens are short-lived and scope-bounded—safer than broad PATs.

Option D — Codespaces’ built-in token (ephemeral, limited)

• In Codespaces, the GITHUB_TOKEN is injected with limited scopes.
• You can run queries via CLI (gh api graphql) or pipe that token into a local tool in the Codespace.

---

Quick start examples

Altair (Desktop)

1. Open Altair → set URL = https://api.github.com/graphql.
2. Headers → add:

   Authorization: Bearer <token>
   X-Github-Next-Global-ID: true   # optional, if you use next-id features
   

3. Click Docs in Altair to introspect schema → autocomplete now works.

GraphiQL (Self-host)

If you self-host GraphiQL (or use Electron builds):

const graphQLFetcher = async (graphQLParams) => {
  const res = await fetch('https://api.github.com/graphql', {
    method: 'POST',
    headers: {
      'Content-Type': 'application/json',
      'Authorization': `Bearer ${process.env.GITHUB_TOKEN}`
    },
    body: JSON.stringify(graphQLParams),
  });
  return res.json();
};

Supply GITHUB_TOKEN at runtime from gh auth token, OAuth exchange, or a GitHub App installation token.

---

Security tips

• Prefer short-lived tokens (GitHub App or OAuth); avoid broad, long-lived classic PATs.
• Keep scopes minimal (read-only where possible).
• Rotate tokens and avoid committing them—use environment variables or the client’s secrets store.

TL;DR:

• Use Altair, GraphiQL, Insomnia, Postman, or VS Code GraphQL tools.
• Skip long-lived PATs by authenticating with GitHub CLI, OAuth App, or GitHub App tokens.
• Point everything at https://api.github.com/graphql and enable schema introspection for autocomplete.

Hope this helps—happy querying!

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[subodhsaha111]

Best Online Graphql Tester: https://devtoolsets.com/graphql-tester
has support for subscriptions as well