OriginChainDB
Database endpoints

Find connected components

Labels every node in a graph schema with its connected component, treating a self-relation as undirected.

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

Find groups that have no connecting linksThis calculation treats the self-relation as undirected.
  1. Select a self-relationChoose the graph's schema and relation.
  2. Group connected nodesFind records reachable within each connected component.
  3. Compare component labelsMatching labels identify membership, not importance.

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
include_rowsbooleanOptional

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

Nodes with the same _component value belong to the same connected component. The self-relation is treated as undirected; the component label is an identifier, not a score.

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.
413Split or reduce the request body.
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