GraphQL Client

Execute GraphQL queries and mutations directly in your browser. Supports variables, headers, auth, and generates cURL commands.

POST
Request
JSON object passed as variables in the request body.
Response
Hit ▶ Execute to run your query
Generated cURL Command
⚠ Browser CORS: Some GraphQL APIs block browser requests. The generated cURL command always works from your terminal. Public APIs like countries.trevorblades.com allow browser access — use those to test.

About GraphQL Query Tester

This tool lets you execute GraphQL queries and mutations against any HTTP endpoint directly from your browser. Enter your GraphQL server URL, write your query or mutation in the editor, supply variables as a JSON object, add any required headers or authentication, and click Execute to see the formatted response with a collapsible JSON tree.

It also generates the equivalent cURL command for every request so you can reproduce it from your terminal or share it with teammates. No data is stored — all requests go directly from your browser to the target GraphQL server.

Common Use Cases

How to Use

  1. Enter your GraphQL endpoint URL in the address bar at the top
  2. Write your query or mutation in the Query tab — use the Load Example button to start with a working query
  3. Switch to the Variables tab and add a JSON object if your query uses $variables
  4. Click "Execute" — expand and collapse JSON nodes in the response to explore nested data

Frequently Asked Questions

Why does the request succeed in cURL but fail in the browser?

GraphQL servers that do not include CORS headers will block browser-initiated requests. cURL bypasses CORS because it is a command-line tool, not a browser. To test from the browser, use a GraphQL API that permits cross-origin requests, such as the built-in countries.trevorblades.com example endpoint.

How do I pass variables to a parameterized query?

Declare your variables in the query signature, for example query GetUser($id: ID!), then switch to the Variables tab and provide a JSON object like {"id": "123"}. The tool merges them into the request body automatically.

What does the GraphQL errors badge mean?

GraphQL can return an HTTP 200 status but still include an errors array in the response body. This means part of the query succeeded and part failed. The red "GraphQL errors" badge appears when the response contains this array so you are not misled by the green HTTP 200 status code.

Advertisement