Skip to main content
Traverse a graph session object using a structured query AST.

POST /revisions/:id/data/query (Command: query_session_graph)

Request Body

Query AST

The query object has two fields: start — a list of one or two elements: ["V"], ["E"], ["V", "<id>"], or ["E", "<id>"].
  • "V" — start from all vertices in the graph (no id) or a single vertex by id.
  • "E" — start from all edges in the graph (no id) or a single edge by id.
steps — each step is a non-empty list where the first element is the step name and the remaining elements are its arguments: Terminal steps (values, properties, project, path, count) convert the working set to a non-element result. Only limit, dedup, and count are valid after a terminal step.

Hard Caps

The server enforces four hard caps on every query regardless of the AST: Exceeding any cap returns graph_traversal_limit_exceeded.

Response

Errors

  • invalid_graph_envelope — the alias does not exist or its value.type is not "graph".
  • invalid_graph_query — the query AST is malformed or contains unsupported step types.
  • graph_traversal_limit_exceeded — the query hit a server-side traversal cap.

Example

See also