Create Subgraph

post/v1/graphs/{graph_id}/operations/create-subgraph

Set fork_parent=true to clone parent graph data into the new subgraph (async, returns a pending OperationEnvelope). Without fork_parent, creates an empty subgraph synchronously.

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
`name`required	string	Alphanumeric name for the subgraph (e.g., dev, staging, prod1)
`display_name`required	string	Human-readable display name for the subgraph
`description`optional	string	Optional description of the subgraph's purpose
`schema_extensions`optional	string[]	Schema extensions to include (inherits from parent by default)
`subgraph_type`optional	SubgraphType	Type of subgraph: 'static' (parent's base + extensions), 'knowledge' (knowledge-only schema), or 'empty' (bare database, no schema). One of: `static`, `knowledge`, `empty` Default: `static`
`metadata`optional	object	Additional metadata for the subgraph
`fork_parent`optional	boolean	If true, copy all data from parent graph to create a 'fork' Default: `false`

Example request

curl

curl -X POST "https://api.robosystems.ai/v1/graphs/{graph_id}/operations/create-subgraph" \
  -H "X-API-Key: $ROBOSYSTEMS_API_KEY" \
  -H "Idempotency-Key: <Idempotency-Key>" \
  -H "Content-Type: application/json" \
  -d '{
  "name": "dev",
  "display_name": "Development Environment"
}'

Responses

200 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