Search and product views

VegaGraph exposes one generic typed graph and several product views. Search finds candidates; a 360 or tailored endpoint provides the governed detail.

Use the dashboard walkthrough to search interactively, then open Entity 360 to inspect a result's identity, facts and relationships.

Search

GET /search?q=net+retention

Use the filters exposed by the endpoint schema to narrow entity type/category, context, lifecycle, source or labels. Results remain authorization-filtered.

A search result is a derived projection. Follow its entity ID to the entity or product-specific detail endpoint before making a governance or operational decision.

Search documents

PUT    /entities/{entity_id}/search-document
GET    /entities/{entity_id}/search-document
DELETE /entities/{entity_id}/search-document

Connectors and indexing jobs replace search documents for an entity. Deleting a document removes it from search without deleting the entity, aspects, evidence or edges.

Only fields approved by the type/aspect search contract should be indexed. Never copy credentials, unrestricted log bodies or raw sensitive payloads into search text.

Tables

GET /tables
GET /tables/{entity_id}
GET /tables/{entity_id}/360
GET /tables/{entity_id}/columns
GET /tables/{entity_id}/path

Table projections combine common schema, ownership, profiling, quality, classification and lineage information. Columns remain field references unless promoted to entities.

KPIs

GET /kpis
GET /kpis/{entity_id}
GET /kpis/{entity_id}/360
GET /kpis/{entity_id}/lineage
GET /kpis/{entity_id}/impact

KPI lineage explains inputs and computation relationships. KPI impact walks downstream consumers and business relationships. The two directions answer different questions and should not be merged into one unlabeled graph.

Services

GET /services
GET /services/{entity_id}
GET /services/{entity_id}/360
GET /services/{entity_id}/dependencies
GET /services/{entity_id}/runtime

The canonical service describes stable ownership, interfaces and meaning. Runtime uses the selected environment/context to show deployments, endpoints, infrastructure and observed state.

Repositories

GET /repositories
GET /repositories/{entity_id}
GET /repositories/{entity_id}/360
GET /repositories/{entity_id}/services

Repository-to-service projections make code ownership and impact visible without treating a repository and a runtime service as the same entity.

Environments

GET /environments
GET /environments/{entity_id}
GET /environments/{entity_id}/360
GET /environments/{entity_id}/runtime

Environment views summarize the context and runtime entities visible within it. Select an explicit context before comparing production and non-production state.

Choosing an endpoint