Materialize Graph

post/v1/graphs/{graph_id}/operations/materialize

Rebuilds LadybugDB from staging tables (file uploads) or extensions OLTP data. Set dry_run=true to preview without changes.

Idempotency: supply an Idempotency-Key header to make safe retries; replays within 24 hours return the same envelope. Reusing the key with a different body returns HTTP 409 Conflict.

Authentication

Authenticate in any one of these ways — not all of them:

API key in the X-API-Key header.
Bearer token in the Authorization header.

Path parameters

Name	Type	Description
`graph_id`required	string	Graph Id

Header parameters

Name	Type	Description
`Idempotency-Key`optional	string	Idempotency-Key

Request body

Required, application/json.

Field	Type	Description
`force`optional	boolean	Force materialization even if already up to date Default: `false`
`rebuild`optional	boolean	Rebuild the graph from scratch, dropping existing data. Required (staged source) when materializing new uploads into a graph that already contains materialized data — staging replays all uploaded files, so a non-rebuild pass would re-copy ingested rows (409). Default: `false`
`dry_run`optional	boolean	Validate tables without writing to the graph Default: `false`
`source`optional	string	Materialization source: 'extensions' for OLTP, omit for DuckDB staging tables
`materialize_embeddings`optional	boolean	Generate vector embeddings during materialization Default: `false`

Example request

curl

curl -X POST "https://api.robosystems.ai/v1/graphs/{graph_id}/operations/materialize" \
  -H "X-API-Key: $ROBOSYSTEMS_API_KEY" \
  -H "Idempotency-Key: <Idempotency-Key>" \
  -H "Content-Type: application/json" \
  -d '{
  "force": false,
  "rebuild": false,
  "dry_run": false,
  "source": "string",
  "materialize_embeddings": false
}'

Responses

202 Successful Response

Field	Type	Description
`operation`required	string	Kebab-case operation name
`operationId`required	string	op_-prefixed ULID for audit and SSE correlation
`status`required	string	Operation lifecycle state One of: `completed`, `pending`, `failed`
`result`optional	any	Command-specific result payload
`at`required	string	ISO-8601 UTC timestamp
`createdBy`optional	string	User ID that initiated the operation (null for legacy callers)
`idempotentReplay`optional	boolean	True when this envelope came from the idempotency cache — the underlying command did not execute again. False on fresh executions. Default: `false`

Status	Meaning
400	Invalid request
401	Authentication required
403	Access denied
404	Resource not found
409	Idempotency-Key conflict — key reused with different body
422	Validation error
429	Rate limit exceeded
500	Internal server error