OneStopList

Gods and goddesses

Apollo Studio GraphQL Sandbox: What It Is & How to Use

Updated November 21, 2026

Apollo Studio’s GraphQL Sandbox is a free, browser-based IDE for exploring and testing GraphQL APIs, acting as the modern replacement for the deprecated GraphQL Playground. It lets you write queries, view schemas, and inspect responses without installing anything, and it’s built into Apollo Studio’s Explorer for both local development and production graphs.

Background: From Playground to Sandbox

Apollo Studio is Apollo’s cloud platform for managing GraphQL supergraphs, offering schema registry, metrics, and observability. For years, developers used GraphQL Playground, a standalone IDE, to test queries. Apollo deprecated Playground in 2020 and integrated a new tool called Explorer into Apollo Studio. The Sandbox is the free, standalone version of that Explorer, designed for local development and quick testing. It’s available at studio.apollographql.com/sandbox and can be used with any GraphQL endpoint, not just Apollo Server.

How the Sandbox Works

The Sandbox connects to a GraphQL endpoint (usually http://localhost:4000/graphql) and provides a full IDE experience. Key features include:

  • Query editor: Write operations with syntax highlighting, auto-completion, and validation.
  • Schema explorer: Browse types, fields, and arguments, and click to add them to your query.
  • Response panel: See results formatted as JSON, with tabs for headers and raw response.
  • Headers editor: Add authentication tokens or other HTTP headers to test protected endpoints.
  • History: Previous operations are saved locally in your browser.

To use it, open the Sandbox URL, enter your endpoint, and start querying. For local servers, ensure CORS is enabled. You can also embed the Sandbox in your own documentation or internal tools using an iframe.

How to Choose: Sandbox vs. Explorer

Both tools share the same underlying code, but they serve different purposes. The Sandbox is ideal for:

  • Local development against a running server.
  • Quick testing of a public GraphQL API without setting up an account.
  • Sharing a query with a colleague via a URL (though the URL doesn’t persist the query by default).

Apollo Studio Explorer is the same interface but connected to a registered graph in Apollo Studio. It adds features like:

  • Saved operations and collections.
  • Integration with schema history and variants.
  • Metrics and tracing for production graphs.
  • Team collaboration and sharing.

If you’re just testing a local API, use the Sandbox. If you’re working with a production graph managed in Apollo Studio, use Explorer.

Common Problems and Solutions

Developers often hit a few snags when using the Sandbox:

  • CORS errors: The Sandbox runs in your browser, so the endpoint must allow cross-origin requests. For Apollo Server, enable cors: true in the server options.
  • Introspection disabled: Some production APIs disable introspection for security. The Sandbox can’t show the schema, but you can still send queries if you know the shape.
  • Authentication: For endpoints requiring auth, add the token in the Headers tab (e.g., Authorization: Bearer <token>).
  • WebSocket subscriptions: The Sandbox supports subscriptions via a separate URL (e.g., ws://localhost:4000/graphql). You may need to configure the connection.

Comparison with Other Tools

The Sandbox is one of several GraphQL IDEs. Here’s how it stacks up:

  • GraphQL Playground: Deprecated, but still works. The Sandbox is more modern and actively maintained.
  • Altair GraphQL Client: A standalone desktop app with similar features, but not integrated with Apollo Studio.
  • Insomnia/Postman: General API clients that support GraphQL, but they lack the schema-aware autocomplete and explorer that the Sandbox provides.
  • GraphiQL: The reference IDE that can be embedded in your own app. The Sandbox is a hosted version with extras.

For most developers, the Sandbox is the fastest way to get started because it requires zero setup.

Cost and Safety Considerations

The Sandbox is completely free to use, with no account required. However, it’s a browser-based tool, so be mindful of security:

  • Never paste sensitive tokens into a public demo or shared URL.
  • If you’re testing a production API, be careful with mutations that could alter data.
  • The Sandbox stores history locally; clear your browser data if you’re on a shared machine.

For production graphs, Apollo Studio offers a free tier, but advanced features like team management and higher metrics retention require a paid plan.

Alternatives and Embedding

If you need a self-hosted or embeddable IDE, consider:

  • GraphiQL: Open-source and embeddable in your own web app.
  • Apollo Sandbox Embed: You can embed the Sandbox in your documentation using an iframe, with options to pre-fill the endpoint and query.
  • Altair: A desktop app that works offline.

For learning, the Sandbox is also a great way to practice GraphQL queries without setting up a server—just point it to a public API like the SpaceX API or the Countries API.

Frequently Asked Questions

Is Apollo Sandbox free? Yes, the Sandbox is free and does not require an Apollo account. You just need a GraphQL endpoint to connect to.

Can I use Apollo Sandbox with any GraphQL API? Yes, as long as the API allows CORS and introspection. It works with any GraphQL server, not just Apollo Server.

How do I add authentication headers in the Sandbox? Click the Headers tab at the bottom of the query editor, then add a header like Authorization: Bearer <your-token>. You can also set default headers in the settings.

Why is my schema not showing in the Sandbox? The API likely has introspection disabled. You can still run queries if you know the schema, but the explorer won’t populate. For local development, ensure introspection is enabled.

Does the Sandbox support subscriptions? Yes, it supports GraphQL subscriptions over WebSocket. You may need to configure the subscription URL in the settings, especially if it differs from the HTTP endpoint.

Can I share a query from the Sandbox? You can copy the URL, but it won’t include the query. To share, you’d need to use Apollo Studio Explorer with saved operations, or copy the query text manually.

Related

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