Does the GraphQL Playground store my queries?
Only the last 10 queries are stored locally in your browser for quick reuse. Nothing is sent to KalpLabs servers.
Test GraphQL APIs with a focused playground. Compose queries, attach variables and headers, and inspect responses without leaving your browser.
No JSON response to display.
Parse OpenAPI specs and explore grouped endpoints, parameters, and schemas visually.
OpenImport Postman collections, run requests locally, and export them as curl commands.
OpenBuild and send HTTP requests with headers, params, auth, and body directly in the browser.
OpenRuns GraphQL queries with variables, headers, schema introspection, and local history in one browser-only workspace.
Accepted input
Accepts a GraphQL endpoint URL, query text, JSON variables, and optional request headers. Query history is stored locally for the last 10 executions.
How to use
Tips
GraphQL workflows often require juggling query editors, variable payloads, and headers for auth. This playground keeps those controls in one place and runs fully in your browser.
Schema introspection makes it easier to explore available queries and mutations when the server permits it. The sidebar highlights available types and fields based on the active endpoint.
History is saved locally so you can quickly revisit prior queries without sending anything to external servers.
Only the last 10 queries are stored locally in your browser for quick reuse. Nothing is sent to KalpLabs servers.
Yes. Add authorization headers in the headers panel and the request will include them when executing queries or introspection.
Some GraphQL servers disable introspection in production or require auth headers. Verify the endpoint and permissions.
KalpLabs uses analytics cookies to improve the experience.