OriginChainDB
Database endpoints

Find broken graph links

Find relation edges whose source or target row is missing. Results are returned in resumable pages.

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

Locate links with missing endpoint recordsContinue truncated scans before treating an empty page as an all-clear.
  1. Select the relationSet scan budget and result limit.
  2. Check link endpointsFind edges with missing source or target rows.
  3. Continue from next_afterResume when the response reports truncation.

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
budgetintegerOptional
limitintegerOptional
afterstringOptional

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

Read dangling for broken links. If truncated is true, continue with next_after; an empty page is not an all-clear when scanning stopped at a budget or page limit.

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.
413Split or reduce the request body.
429Honor Retry-After when present; back off.
500Check the outcome before retrying a write.
501Check deployment support for this operation.
503Honor Retry-After when present; check write outcomes.
ยฉ 2026 Silicoyn Technologies Pvt Ltd