Browse the API reference

Presign a File Upload

post/v1/graphs/{graph_id}/operations/create-file-upload

Part of Content Operations.

Presign an S3 URL for direct upload and register the file. After uploading to the returned URL, call POST /operations/ingest-file to stage it into DuckDB. The staging table is auto-created if missing. Not allowed on entity graphs or shared repositories.

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

NameTypeDescription
graph_idrequiredstringGraph Id

Header parameters

NameTypeDescription
Idempotency-KeyoptionalstringIdempotency-Key

Request body

Required, application/json.

FieldTypeDescription
file_namerequiredstring

File name to upload

content_typeoptionalstring

File MIME type

Default: application/x-parquet

table_nameoptionalstring

Table name to associate file with (required for first-class /files endpoint)

file_size_bytesoptionalinteger

Size of the file about to be uploaded, in bytes. Optional; when supplied, an over-limit file is rejected here instead of after it has been pushed to S3 and rejected by ingest-file. Advisory only — the authoritative check measures the object after upload.

Example request

curl
curl -X POST "https://api.robosystems.ai/v1/graphs/{graph_id}/operations/create-file-upload" \
  -H "X-API-Key: $ROBOSYSTEMS_API_KEY" \
  -H "Idempotency-Key: <Idempotency-Key>" \
  -H "Content-Type: application/json" \
  -d '{
  "content_type": "application/x-parquet",
  "file_name": "entities.parquet",
  "table_name": "Entity"
}'

Responses

200 Successful Response

FieldTypeDescription
operationrequiredstring

Kebab-case operation name

operationIdrequiredstring

op_-prefixed ULID for audit and SSE correlation

statusrequiredstring

Operation lifecycle state

One of: completed, pending, failed

resultoptionalany

Command-specific result payload

atrequiredstring

ISO-8601 UTC timestamp

createdByoptionalstring

User ID that initiated the operation (null for legacy callers)

idempotentReplayoptionalboolean

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

Default: false

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