OneStopList

Gods and goddesses

Apollo Studio Explorer: What It Does and How to Use It

Updated November 21, 2026

Apollo Studio Explorer is a visual, graph-based interface within Apollo GraphQL’s developer platform (Apollo Studio) that lets you browse, understand, and debug the schema of a GraphQL API. Instead of reading raw SDL (Schema Definition Language) text, you interact with a node-and-edge diagram showing types, fields, and their relationships, making it easier to see how your data connects before you write queries.

What Apollo Studio Actually Is

Apollo Studio is a cloud-hosted suite of tools for teams building GraphQL APIs. It is not a local library or a command-line tool; it is a web application that connects to your running GraphQL server (often via Apollo Server) and ingests your schema and operation traces. The platform provides several features: schema history and versioning, operation metrics (like latency and error rates), a query planner for federated graphs, and the Explorer, which is the interactive documentation and query-building tool. The Explorer is the part most developers open daily, because it replaces the older GraphQL Playground and the default GraphiQL interface for many teams.

How the Explorer Differs from GraphiQL or Playground

If you have used GraphiQL or GraphQL Playground, you know they show a schema on the left (collapsible type trees) and a query editor on the right. Apollo Studio Explorer improves on that in three ways. First, it renders the schema as a graph: you can click a type like User and see its fields, then click a field that returns Post and see that type’s fields, with edges drawn between them. Second, it includes a built-in query builder that lets you pick fields with checkboxes and generates the query string for you. Third, it shows real-time execution results in a panel, including errors and response headers, and it can save queries to a collection for your team. The Explorer also understands federated graphs, so if your API uses Apollo Federation, it shows which subgraph owns which field.

How to Open and Use the Explorer

You do not install the Explorer; you access it through the Apollo Studio web app. The typical workflow is:

  • Create or log into an Apollo Studio account and create a graph (a project representing your API).
  • Register your GraphQL server with Studio by adding the Apollo Server plugin or using the Apollo CLI to push your schema.
  • Open the graph in Studio and click the “Explorer” tab in the left sidebar.
  • Select an endpoint (production, staging, or a local URL) from the dropdown at the top.
  • Use the “Build” panel on the left to expand types and check fields; the query editor updates automatically.
  • Click the run button to execute the query against the chosen endpoint and see the response on the right.

For a quick test without a server, Studio offers a “Sandbox” that lets you paste any GraphQL endpoint URL and explore its schema, even if that server is not registered with Apollo. This is useful for public APIs like GitHub’s GraphQL API or SpaceX’s public API.

Key Features You Will Actually Use

The Explorer is more than a schema browser. Its most useful features for daily work include:

  • Field-level search: Type a field name like email and the Explorer highlights it across all types, which is faster than scrolling long SDL.
  • Argument and variable help: When you add a field that requires arguments (like filter or id), the Explorer shows input fields and lets you define GraphQL variables in a separate pane.
  • Operation history: Every query you run is saved, so you can return to a previous test without retyping it.
  • Schema reference panel: Click any type or field to see its description, deprecation status, and whether it is part of a federation subgraph.
  • Copy as cURL or code: The Explorer can generate a ready-to-run request in cURL, JavaScript (fetch), or other languages, which helps when you need to reproduce a query outside the browser.

Common Problems and Misconceptions

One frequent misconception is that the Explorer only works with Apollo Server. That is false: it works with any GraphQL server that exposes a standard /graphql endpoint, including Express GraphQL, Hasura, and AWS AppSync, as long as you provide the URL in the Sandbox. Another issue is that the Explorer does not show your server’s custom directives (like @auth) unless you have pushed them as part of your schema; Apollo Studio only knows what your server reports. A third problem is that running expensive queries in the Explorer can hit your production server and cause load; the Explorer does not throttle requests, so be careful when testing against a live API. Finally, some users expect the Explorer to show real-time subscriptions (like WebSocket updates). It does support subscriptions, but you must configure your server’s subscription endpoint and the browser must support WebSockets; it is not as seamless as query execution.

How the Explorer Handles Federated Graphs

If your API uses Apollo Federation (a way to combine multiple GraphQL services into one unified graph), the Explorer becomes especially valuable. It shows a field’s origin subgraph (for example, User.email might come from the “users” service while User.orders comes from the “orders” service). You can also see the query plan for a request—a step-by-step breakdown of which subgraphs are called and in what order—which helps debug performance issues. This is a feature that GraphiQL and Playground simply do not have, so teams using Federation often adopt Studio Explorer specifically for this view.

Costs and Limits

Apollo Studio has a free tier and paid plans. As of the current public pricing, the free tier includes a limited number of schema checks and daily operation reports, and it allows a certain number of graph members. The Explorer itself is free to use on any plan; you are not charged per query. Paid plans add features like advanced security policies, longer data retention, and more team seats. For a solo developer or a small project, the free tier is sufficient to use the Explorer fully. For enterprise teams, the cost scales with the number of monthly tracked operations, so large APIs can incur significant charges—check Apollo’s official pricing page for current numbers because they change.

Alternatives to Apollo Studio Explorer

If you do not want to use Apollo’s cloud service, several alternatives exist. The open-source GraphiQL is a lightweight in-browser IDE that you can embed in your own app; it lacks the graph view and federation support but is fully local. GraphQL Playground (now deprecated) was a popular alternative with a nicer UI than GraphiQL but is no longer actively maintained. Altair GraphQL Client is a desktop and browser extension that supports subscriptions, file uploads, and environment variables, making it a good choice for testing. Insomnia and Postman both have GraphQL clients that let you write queries and inspect schemas, though their schema browsing is less visual. For teams that want no cloud dependency, GraphiQL with the graphql-voyager library can render a schema graph locally, but you lose the metrics and collaboration features that Studio provides.

Frequently Asked Questions

Does Apollo Studio Explorer work with any GraphQL server? Yes, for basic exploration. You can use the Sandbox and paste any public GraphQL endpoint URL to browse its schema and run queries. However, advanced features like schema history and operation metrics require your server to be registered with Apollo Studio, which usually means adding the Apollo Server plugin.

Is the Explorer the same as the Schema Reference? No. The Schema Reference is a static, text-based list of all types and fields, similar to generated documentation. The Explorer is interactive: it lets you build queries visually, run them, and see results. The Reference is useful for reading descriptions, while the Explorer is for testing.

Can I use the Explorer for local development? Yes. In the Explorer, you can set the endpoint to http://localhost:4000/graphql (or your local port) and run queries against your local server. This works as long as your server allows CORS requests from the Apollo Studio domain; if not, you may need to configure CORS in your server code.

Why does my schema not show up in the Explorer? The most common reason is that you have not pushed your schema to Studio. Run rover subgraph introspect or use the Apollo CLI to publish your schema. Also check that you selected the correct graph and variant (like production or staging) in the top dropdown.

Does the Explorer store my queries? Yes, it saves your operation history in your Apollo Studio account, and you can also save queries to a shared collection for your team. These are stored on Apollo’s servers, so do not put secrets or sensitive data in queries if you are on a free tier with less strict data handling.

Is the Explorer safe to use against a production API? It is safe in the sense that it only sends normal GraphQL requests, but it does not rate-limit you. Running a deeply nested query or a large list fetch can put load on your production database. Use the Explorer carefully, and consider testing against a staging environment first.

Related

How pages are sourced and corrected: Sources and editorial policy.