Error

A valid request URL is required to generate request examples

{
  "error": "Some error occurred, this is an example of error message",
  "status": 500,
  "traceback": [
    "<string>"
  ]
}

{
  "error": "Some error occurred, this is an example of error message",
  "status": 500,
  "traceback": [
    "<string>"
  ]
}

{
  "error": "Some error occurred, this is an example of error message",
  "status": 500,
  "traceback": [
    "<string>"
  ]
}

{
  "error": "Some error occurred, this is an example of error message",
  "status": 500,
  "traceback": [
    "<string>"
  ]
}

{
  "error": "Some error occurred, this is an example of error message",
  "status": 500,
  "traceback": [
    "<string>"
  ]
}

operation

Write to a subprocess's stdin and/or close it

Writes a chunk to the stdin of a live process inside the running instance — spid=1 targets the main process, ≥2 the exec’d children. Requires the process to have been started with stdin.close=false; otherwise its pipe is already at EOF and the call returns 409.

close=true (the default) signals EOF after writing value; an empty value with close=true just closes the pipe. A client that serializes its own requests gets ordered writes; concurrent requests to the same spid are safe but their order is unspecified.

A 504 means the guest write timed out mid-call — the chunk may or may not have been delivered (e.g. the process stopped reading and the pipe is full), so blind retries can duplicate data.

POST

/

operations

/

{operationId}

/

subprocesses

/

{spid}

/

stdin

Error

A valid request URL is required to generate request examples

{
  "error": "Some error occurred, this is an example of error message",
  "status": 500,
  "traceback": [
    "<string>"
  ]
}

{
  "error": "Some error occurred, this is an example of error message",
  "status": 500,
  "traceback": [
    "<string>"
  ]
}

{
  "error": "Some error occurred, this is an example of error message",
  "status": 500,
  "traceback": [
    "<string>"
  ]
}

{
  "error": "Some error occurred, this is an example of error message",
  "status": 500,
  "traceback": [
    "<string>"
  ]
}

{
  "error": "Some error occurred, this is an example of error message",
  "status": 500,
  "traceback": [
    "<string>"
  ]
}

Authorizations

Authorization

string

header

required

IAM bearer token issued by the Nebius IAM service. Sent as Authorization: Bearer <iam-token>. Must be combined with the Project header (see IAMProjectHeader).

This is the recommended authentication scheme for new clients.

Project

string

header

required

Nebius project ID associated with the IAM token. Required together with IAMBearerAuth. Identifies the project context the request is scoped to.

Path Parameters

operationId

string<uuid>

required

The ID of the operation A UUID string

Example:

"12345678-9abc-baba-deda-0123456789ab"

spid

integer

required

Spawn id (1 = main process; ≥2 = exec'd children).

Required range: x >= 1

Body

application/json

Stdin payload. Delivery to the child is always complete — stdin is never truncated on its way to the process. Only the recorded stdin events in the subprocess event log are capped by truncate_output_at, same as stdout/stderr. This schema also carries a close flag controlling the pipe's EOF.

value

string

required

Content to write to stdin (may be empty for a close-only request)

Example:

"aGVsbG8K"

encoding

enum<string>

default:ascii

Encoding of the content

Available options:

ascii,

base64

close

boolean

default:true

true (default) closes stdin (EOF) after writing value — the pre-existing one-shot behavior. false keeps the pipe open so more data can be sent later via POST /operations/{operationId}/subprocesses/{spid}/stdin.

Response

Chunk written (and/or stdin closed).