GET /api/query

Run a Cypher query from a URL parameter — for quick checks and browser-pasteable links. Request and response reference with code in five languages.

Updated July 2026API Reference

GET /api/query Documentation

GET /api/query runs the same query functionality as POST /api/query, with the Cypher passed as the q URL parameter. It is handy for quick checks and links you can paste into a browser.

Use POST for anything real: it avoids URL-encoding the whole query, has no URL length limit, and carries parameters cleanly. Use GET for one-off reads and debugging. A GET without q returns 400.

Base URL: https://graph.whisper.security. Authentication is shared across the API and covered on the API Reference index.

Request
PartValue
Query parameter qThe Cypher query, URL-encoded. Required.
X-API-Key headerOptional. Anonymous tier if omitted.
User-Agent headerRecommended, to avoid a WAF 403.

Call it

 
curl -s -A "whisper-client/1.0" \
  -H "X-API-Key: $WHISPER_API_KEY" \
  "https://graph.whisper.security/api/query?q=RETURN%201%20AS%20n"

The response is the same envelope as POST:

{"columns": ["n"], "rows": [{"n": 1}], "statistics": {"rowCount": 1, "executionTimeMs": 0}}

For the full request body, parameter binding, and batch statements, see POST /api/query. For graph-wide counts, see GET /api/query/stats.

PreviousPOST /api/queryNextAPI Reference