OriginChainDB
Database endpoints

Find a path

Reports whether one node can reach another along a relation within a depth limit.

GET /v1/tenants/{tenant}/graph/{schema}/path

Check whether one record reaches anotherA truncated search cannot prove that no path exists.
  1. Select source and destinationChoose the relation and maximum search depth.
  2. Check bounded reachabilityFollow links within the requested depth.
  3. Read reachable and truncatedThis response does not contain an ordered route.

Before you start

Use your database bearer token.

Connection setup

Register the schema and relation, then add their rows. The examples use demo.people, its bidirectional follows relation, and linked rows u1, u2 and u3.

Path parameters

FieldTypeRequired
tenantstringRequired
schemastringRequired

Query parameters

FieldTypeRequired
relstringRequired
srcstringRequired
dststringRequired
max_depthintegerOptional

Headers

FieldTypeRequiredDescription
x-oc-db-userstringOptionalActing database user (role, grant and row-policy checks). Send with x-oc-db-key.
x-oc-db-keystringOptionalAPI key of the x-oc-db-user user.

Read the result

reachable answers the reachability question within the requested depth. Check truncated before interpreting a negative result as proof that no path exists. This response does not contain an ordered path.

Response statuses

HTTP status reference
StatusWhat to do
200OK
400Correct the request before retrying.
401Check the credential and Authorization header.
402Check feature access or available credits.
403Check tenant access, roles and permissions.
404Check the resource ID and API route.
408Reduce query work or adjust the timeout.
429Honor Retry-After when present; back off.
499The client cancelled the request.
500Check the outcome before retrying a write.
503Honor Retry-After when present; check write outcomes.
ยฉ 2026 Silicoyn Technologies Pvt Ltd