OriginChainDB
Database endpoints

Walk a graph at random

Follow a seeded random walk from a node, optionally using Node2Vec bias.

GET /v1/tenants/{tenant}/graph/{schema}/random-walk

Sample a journey through connected recordsThe walk can revisit nodes; it is not a shortest-path result.
  1. Choose a start and seedSet the number of steps and optional walk bias.
  2. Follow sampled linksWalk through the relation one step at a time.
  3. Read the visited sequenceReuse the seed on unchanged data for reproduction.

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
startstringRequired
stepsintegerRequired
seedintegerRequired
pnumberOptional
qnumberOptional

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

walk is the sequence of visited node keys. Nodes may repeat; it is a sampled walk rather than a shortest or loop-free path. Use the same seed when reproducing a walk on unchanged data.

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