OriginChainDB
Database endpoints

List reverse neighbors

Returns the nodes that point to a node along a relation (its inbound edges).

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

Find records pointing into a targetReturned keys describe inbound neighbors, not complete rows.
  1. Select the target recordSupply its primary key and relation.
  2. Follow incoming linksFind nodes that point toward this record.
  3. Read their primary keysFetch their rows separately when needed.

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
pkstringRequired

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

The array contains keys of nodes pointing into the selected node along this relation. These are inbound neighbors, not full row objects.

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.
502Check service availability and the write outcome.
503Honor Retry-After when present; check write outcomes.
ยฉ 2026 Silicoyn Technologies Pvt Ltd