Webhook HMAC Signer
Sign and verify GitHub, Stripe, and Slack webhook signatures locally.
OpenClean up a GraphQL document, sanity-check its variables and get a cURL command to run it.
Add queries, mutations, and variable JSON.
Catch brace issues and unused variables locally.
Depth and breadth heuristics flag expensive trees.
Copy a ready-to-run request for your GraphQL endpoint.
A mobile client sends a query that times out on the gateway, and the only copy you have is one minified line from a log. Formatting it, counting how deep the selections go and seeing what the pagination arguments multiply to tells you quickly whether the query or the server is at fault.
Paste a query, mutation, subscription or fragment document. If the brackets balance, the formatted version appears on the right with consistent indentation and string literals left intact. If they do not, formatting pauses and the report lists each problem with its line and column. The analysis lists every operation by name and line, warns when an anonymous operation sits alongside others, and checks variables both ways: declared but never used, and used but never declared. Supply variables JSON and it also flags required variables you left out and extra keys nothing declares.
The cost estimate counts each field as one unit and multiplies by pagination arguments such as first, last, limit or take on the selections above it, alongside nesting depth and the widest selection set. It works without a schema, so it cannot tell you whether a field exists, but it is good at spotting queries that fan out. Enter an endpoint and an optional Authorization value and the cURL panel builds a POST with the query and variables as a JSON body. If the variables refuse to parse, the JSON beautifier and syntax checker shows where, and the API toolkit has helpers for the REST side of the same service.
This page sends no requests; the cURL command is plain text for you to run yourself.
Keyboard shortcut
Answers for this tool. For site-wide help, open the FAQ hub.
No schema is loaded, so field names and argument types are not validated. The checks cover syntax, variable usage and the shape of the query.
The variables are replaced with an empty object and the report marks the JSON as invalid. Fix the JSON and the export updates on the next run.
Depth above 6 is a warning and above 10 is a failure. Many gateways cap depth in roughly that range, so the thresholds give early notice before a query is rejected.