ArangoDB v3.13 is under development and not released yet. This documentation is not final and potentially incomplete.
HTTP interface for edges
The Edge API lets you retrieve the connected edges of a single vertex, optionally restricted to incoming or outgoing edges
You can use the general Document API to create,
read, modify, and delete edge documents. The only difference to working with
vertex documents is that the _from
and _to
attributes are mandatory and
must contain document identifiers.
The Edge API is useful if you want to look up the inbound and outbound edges of a vertex with low overhead. You can also retrieve edges with AQL queries, but queries need to be parsed and planned, and thus have an overhead. On the other hand, AQL is far more powerful, letting you perform graph traversals, for instance.
Addresses of edges
Edges are a special variation of documents and you can access them like any document. See Addresses of documents for details.
Get inbound and outbound edges
vertex
.Examples
Any direction
curl --header 'accept: application/json' --dump - http://localhost:8529/_api/edges/edges?vertex=vertices/1
In edges
curl --header 'accept: application/json' --dump - http://localhost:8529/_api/edges/edges?vertex=vertices/1&direction=in
Out edges
curl --header 'accept: application/json' --dump - http://localhost:8529/_api/edges/edges?vertex=vertices/1&direction=out