Content Operations

Stage an Uploaded File

Mark an uploaded file ready and stage it into DuckDB. Small files stage directly (sync); large files stage via a background job (returns a pending envelope with an operation_id to monitor). Set ingest_to_graph to auto-materialize into the graph after staging; that write takes the graph's materialize lock, so it returns 409 while another materialization of the graph is running.

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.

post/v1/graphs/{graph_id}/operations/ingest-file

Request

  • Base URL: https://api.robosystems.ai (the document declares no server; this is the origin it was published from)
  • URL: https://api.robosystems.ai/v1/graphs/{graph_id}/operations/ingest-file
  • Auth: one of:
    • API key in header X-API-Key
    • HTTP bearer

Path parameters

graph_idstring required

Headers

Idempotency-Keystring nullable

Request body

file_idstring required

Uploaded file id to ingest

ingest_to_graphboolean

Auto-materialize into the graph after DuckDB staging. Refused with 409 while another materialization of the graph is running.

Response

Successful Response

operationstring required

Kebab-case operation name

operationIdstring required

op_-prefixed ULID for audit and SSE correlation

status'completed' | 'pending' | 'failed' required

Operation lifecycle state

resultunknown
atstring required

ISO-8601 UTC timestamp

createdBystring nullable

User ID that initiated the operation

idempotentReplayboolean

True when this envelope came from the idempotency cache — the underlying command did not execute again. False on fresh executions.

Changes

No recorded changes to this operation across all 1 revision of this API.