Skip to main content
Reference
Send one Cypher statement to a local instance and print the JSON response, or plan it without running it. Local only.

Usage

Exactly one of -e and --file is required. See the Cypher guide for the supported language profile.

Arguments

Options

Input (pick one)

Statement

Connection

Output

Behavior

Target resolution

  • With no INSTANCE, the CLI uses the dev instance, then the only instance, then a picker in a terminal.
  • The instance must be local. A Cloud instance fails with Cypher CLI requests currently require a local instance; send Cypher to Helix Cloud through an SDK or POST /v2/cypher.

Requests

  • The statement posts to the local, auth-disabled /v2/cypher, or /v2/cypher/explain with --explain.
  • --parameters must be a JSON object; any other JSON value fails before the request is sent.
  • A 404 means the server predates Cypher, and the error asks you to upgrade it. Cypher needs the ghcr.io/helixdb/helixdb:v0.0.13 image or later.

Output

  • A successful response goes to stdout as syntax-highlighted, pretty-printed JSON with columns and rows, or the plan under --explain. --json prints compact JSON instead.
  • A non-2xx response fails with the HTTP status and the error body, including the Cypher error error, msg, and details.

Examples