Upload Session Object - BlobHub

Upload an object to the session storage.

POST `/revisions/:id/data/command` (Command: `upload_session_object`)

Request Body

Parameter	Type	Required	Description
`engine`	string	Yes	Must be `workflow_blobhub`.
`command`	string	Yes	Must be `upload_session_object`.
`session_id`	string	Yes	The ID of the session.
`alias`	string	Yes	Path-style alias for the object (see grammar note below).
`value`	object	Yes	The JSON object to store.

The alias must conform to the session-object alias grammar: one or more /-separated segments of A–Z, a–z, 0–9, ., _, -, @; 1–256 characters total; no segment may be . or ... An alias outside the grammar returns 400 invalid_session_object_alias. A successful upload fires a session_object_modified session event.

Response

Returns {"status": "success"} — no body beyond the status.

When value.type is "thread", this command creates or updates the thread envelope only. Items are appended via post_session_thread_item. Deleting the envelope cascades and removes all items.

When value.type is "graph", this command creates or updates the graph envelope only. Elements (vertices and edges) are managed via the six graph commands. Deleting the envelope cascades and removes all elements. See the graph session object for the envelope and element schema.

Example

{
  "engine": "workflow_blobhub",
  "command": "upload_session_object",
  "session_id": "sess_001",
  "alias": "config",
  "value": { "debug": true }
}

{
  "status": "success"
}

See also

BlobHub Worker — thread handoff — set workspace.agent_type, workspace.work_folder, and agent.state = "pending" on a thread envelope to hand it off to a BlobHub Worker.
BlobHub Worker — the worker session object — the worker uploads a worker-aliased session object as its per-session affinity lock and activity log.