Sita Docs
  1. Overview
  2. System
  3. API
  4. Graphs & Structural

API

Graphs & Structural API

Implemented

Structural Memory is served as paged serialisations, not a live Neo4j session from the browser. Pagination caps JSON, not the serialisation work.

Framework03

Why this exists

Why this API boundary exists

Structural Memory is served as paged serialisations, not a live Neo4j session from the browser. Pagination caps JSON, not the serialisation work.

Endpoints

GET/projects/{project_id}/structural/summaryImplemented

Structural counts and coverage, no full graph.

Auth: clerk

Framework03

services/api/app/routes/structural.py

GET/projects/{project_id}/structural/elementsImplemented

Paged structural elements.

Auth: clerk

services/api/app/routes/structural.py

GET/projects/{project_id}/structural/relationsImplemented

Paged structural relations.

Auth: clerk

services/api/app/routes/structural.py

GET/projects/{project_id}/structural/graphImplemented

Paged full graph serialisation.

Auth: clerk

services/api/app/routes/structural.py

POST/projects/{project_id}/structural/serialisationsImplemented

Record a graph serialisation row in Postgres.

Auth: clerk

services/api/app/routes/structural.py

GET/projects/{project_id}/structural/serialisationsImplemented

List serialisation records.

Auth: clerk

services/api/app/routes/structural.py