Skip to developer tool
DEVELOPER TOOLKIT APIS & WEB

GraphQL Query & Response Explorer

Inspect a GraphQL operation from the browser with an explicit endpoint, method, variables and headers. Review responses locally, cancel pending requests and reuse a JSON request envelope in another client.

Browser-based · No account required · Copy and export

Open workspace Read the guide
BUILT FOR THE DETAILS
  1. 01Add your input
  2. 02Inspect & adjust
  3. 03Use your result
Explore all 56 tools

Workspace

PixelOkay · Developer tools

This sends the query directly from your browser to the endpoint. CORS must allow the request; avoid entering production secrets on shared devices.

How to use GraphQL Query & Response Explorer

  1. Enter an HTTP(S) endpoint, operation document and optional operation name. Supply variables and headers as JSON objects.
  2. Choose POST for mutations or GET for queries, set a timeout and choose whether to format the response.
  3. Send only when ready. Inspect the HTTP result and body, or cancel the request. Copy the request envelope without its headers to reuse the operation.

When to use this tool

Inspect a query response or a mutation payload from an endpoint you control. Requests go directly to that endpoint, including any headers or credentials you enter; CORS and browser restrictions still apply.

An HTTP response and a GraphQL result are separate signals

A GraphQL server can return HTTP 200 with an errors array in the JSON body. Inspect both the status and payload. POST sends a JSON envelope containing query, variables and optionally operationName. GET encodes those values in the URL and is blocked here for documents containing mutation or subscription operations.

Worked example

query Item($id: ID!) { item(id: $id) { id name } }
Variables: {"id":"123"}
POST envelope keys: query, variables, operationName (optional)

Limits and output checks

The endpoint must permit the browser origin under CORS. This is an HTTP request explorer, not schema autocomplete or a WebSocket subscription client. Response bodies are bounded to 5 MiB. A timeout or cancellation does not guarantee that a server-side operation was rolled back. Headers may contain sensitive credentials.

Reference: GraphQL over HTTP.

Frequently asked questions

Does opening this page send my query?

No. Sending requires the request action. No schema introspection or automatic endpoint probing is performed.

Why does a request work in another client but fail here?

Browsers enforce CORS, restricted headers and network policies that a command-line client may not enforce.

What is copied in the request envelope?

The query, parsed variables and optional operation name. Authentication headers are excluded, though variables or query text can themselves contain sensitive data.