OneStopList

Gods and goddesses

Apollo Studio Sandbox: What It Is and How to Use It

Updated November 17, 2026

Apollo Studio Sandbox is a free, web-based GraphQL IDE that lets you explore, test, and debug GraphQL APIs without needing to set up a local development environment. It is part of Apollo GraphQL’s suite of developer tools, designed to make it easy to interact with any GraphQL endpoint directly from your browser.

Background: Apollo and the GraphQL Ecosystem

Apollo is a company that builds tools and libraries for GraphQL, a query language for APIs that was created by Facebook in 2012 and open-sourced in 2015. GraphQL allows clients to request exactly the data they need, which can reduce over-fetching and simplify client-server communication. Apollo’s products include Apollo Client (for front-end state management and data fetching), Apollo Server (for building GraphQL APIs), and Apollo Studio, a cloud platform for schema management, observability, and collaboration. The Sandbox is a core part of Apollo Studio, but it can be used independently—you don’t need an Apollo account to use the basic features.

How Apollo Studio Sandbox Works

The Sandbox is essentially a GraphQL playground, similar to tools like GraphiQL or GraphQL Playground, but with additional features tailored for modern development. When you open the Sandbox, you can enter a GraphQL endpoint URL (e.g., https://example.com/graphql) and connect to it. The Sandbox will fetch the schema (if introspection is enabled) and provide a rich interface for writing queries, mutations, and subscriptions.

Key features include:

  • Schema explorer: A sidebar that shows all types, fields, and arguments, with documentation and descriptions pulled from the schema.
  • Query editor: An editor with syntax highlighting, autocompletion, and validation as you type.
  • Response panel: Displays the JSON response, with formatting and error highlighting.
  • Headers and variables: You can set HTTP headers (e.g., authentication tokens) and pass variables to your queries.
  • History: Your past operations are saved locally in the browser, so you can revisit them.
  • Collection sharing: You can save operations to a collection and share them via a link, which is useful for collaboration.

How to Use Apollo Studio Sandbox

Using the Sandbox is straightforward. Here are the typical steps:

  1. Open the Sandbox at studio.apollographql.com/sandbox.
  2. In the URL bar at the top, enter your GraphQL endpoint (e.g., https://countries.trevorblades.com/graphql). If you don’t have one, you can use a public demo endpoint like the Countries API.
  3. Click the “Connect” button. The Sandbox will attempt to introspect the schema and load it into the explorer.
  4. Start writing a query in the editor. For example, with the Countries API, you could write: { countries { name code } }.
  5. Click the “Run” button (or press Ctrl+Enter) to execute the query. The response will appear on the right.

The Sandbox also supports subscriptions, but note that they require a WebSocket connection, which may not work with all endpoints.

Choosing the Right GraphQL IDE

Apollo Studio Sandbox is not the only GraphQL IDE available. Developers often compare it with alternatives:

  • GraphiQL: The original GraphQL IDE from Facebook, often embedded in tools. It’s lightweight but lacks some advanced features like schema explorer.
  • Altair GraphQL Client: A feature-rich desktop and web client with support for multiple environments, subscriptions, and plugins.
  • Insomnia: A REST client that also supports GraphQL, with a focus on API testing and automation.
  • Postman: Similar to Insomnia, but with a larger ecosystem for API development.

Choose the Sandbox if you want a browser-based tool with excellent schema exploration and sharing capabilities, and if you’re already using Apollo Studio for monitoring. Choose a desktop client if you need offline support or advanced scripting.

Common Problems and Solutions

Users often encounter a few issues when using the Sandbox:

  • Introspection disabled: If the server has introspection disabled (common in production), the Sandbox cannot load the schema. You’ll see an error like “Cannot query field ‘introspection’.” In that case, you can still send queries if you know the schema, but autocompletion won’t work.
  • CORS errors: The Sandbox runs in your browser, so the API must allow cross-origin requests. If you get a CORS error, you’ll need to configure the server to allow requests from https://studio.apollographql.com.
  • Authentication: To send authenticated requests, you need to set the appropriate headers (e.g., Authorization). You can do this in the “Headers” tab. For more complex auth flows, you might need to use a proxy or a desktop client.
  • Subscriptions not working: Subscriptions require a WebSocket endpoint. Some servers don’t support that, or the Sandbox may need a specific URL for the subscription (often the same URL but with a different protocol). Check the server’s documentation.

Costs and Limitations

Apollo Studio Sandbox is completely free to use. There is no charge for accessing the Sandbox, and you don’t need an Apollo account to use it. However, if you want to save operations to a collection and share them, you’ll need to create a free Apollo Studio account. That’s it—no hidden costs.

One limitation is that the Sandbox is browser-based, so it relies on an internet connection. Also, it doesn’t have some advanced features like environment variables or scripting that you might find in desktop clients. But for most development and testing purposes, it’s more than sufficient.

Safety and Security Considerations

When using the Sandbox, you should be mindful of security. Since it’s a web tool, any queries you run are executed against the actual API. If you’re working with a production API, be careful not to run destructive mutations that could alter data. Also, the Sandbox stores your operation history in your browser’s local storage, so if you’re on a shared computer, others might see your queries. Avoid entering sensitive credentials in the headers if you don’t want them stored.

For production debugging, it’s safer to use a local tool or a proxy, and always ensure that your API has proper authorization and rate limiting.

Frequently Asked Questions

Is Apollo Studio Sandbox the same as GraphQL Playground?

No, but they are similar. GraphQL Playground was a separate tool that has been deprecated; Apollo Studio Sandbox is its successor, with a different interface and additional features like schema explorer and sharing. If you’ve used GraphQL Playground before, you’ll find the Sandbox familiar but more polished.

Can I use Apollo Studio Sandbox with any GraphQL API?

Yes, as long as the API is accessible over HTTP and allows introspection (or you know the schema). The Sandbox is not tied to Apollo Server; it works with any GraphQL endpoint, including those built with other libraries like GraphQL Yoga or Mercurius.

Do I need an Apollo account to use the Sandbox?

No, you can use the Sandbox without an account. However, creating a free account lets you save operations to collections and share them with others. It also integrates with Apollo Studio’s other features like schema history and metrics.

How do I share a query from the Sandbox?

You can save a query to a collection (requires an account), then click the share icon to get a link. Alternatively, you can copy the query text and share it manually. The Sandbox also supports generating a shareable link for the entire workspace, but that may require a paid plan.

Why is my query not returning any data?

This could be due to several reasons: the endpoint URL is incorrect, the server is down, the query is malformed, or you don’t have permission to access the data. Check the response panel for errors, and verify that your headers include any necessary authentication. Also, make sure the query matches the schema (e.g., field names are case-sensitive).

Related

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