nodes

Export status: running/complete/failed (provider errors verbatim)

Status of an export (export_data): "running" (with bytes_transferred, plus files_done/files_total on a platform-storage tree export), "complete" ({total_bytes, dest}), or "failed" with the provider's real error relayed verbatim - an access failure names the connection so a human can fix it. Status checks never wake a stopped node; an export interrupted by node stop or worker loss reports "failed" honestly and is safe to re-run (re-call export_data; the destination object is replaced, never doubled - and a tree export resumes, skipping objects already landed).

get/preview/nodes/{name}/data-exports/{id}

Request

  • Base URL: https://autoresearch.sfcompute.com
  • URL: https://autoresearch.sfcompute.com/preview/nodes/{name}/data-exports/{id}
  • Auth: HTTP bearer

Path parameters

namestring required

Node name (from list_nodes).

idstring required

Export id from export_data (e.g. "exp-4kd93").

Query parameters

workspacestring

Act in this workspace (its slug). Omitted: the token's bound workspace, then the organization's default. Never ambient - there is no switch-workspace mutation on this door.

Response

The capability's JSON result.

objectstring

The resource type, when the result is one resource.

Changes

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