dots.v2.harnessRuntime.sessions.bySession_id().sandbox.exec.byExec_id().stdin.post()
Generated on 18 Nov 2026
from DoTs version
v1.25.0
Usage
client.v2.harnessRuntime.sessions.bySession_id(session_id).sandbox.exec.byExec_id(exec_id).stdin.post(body: Write_exec_stdin_request, requestConfiguration?: RequestConfiguration<object>): Promise<undefined | Write_exec_stdin_response>Description
offset is required and is the count of stdin bytes already accepted.
An equal offset appends. A lower offset retries and trims the overlap. A higher offset returns 409.
data is base64. eof closes stdin. A write needs data, eof, or both. Each write is at most 1 MiB.
The exec id comes from the started event on the exec stream.
An unknown or finished exec returns 404.
A closed stdin, an offset gap, or a session that cannot accept interactive stdin returns 409.
Parameters
Path Parameters
session_idstring requiredExample:
a1b2c3d4-e5f6-7890-abcd-ef1234567890The session UUID.
exec_idstring requiredExample:
01932a6e-7b4c-7d2e-8f10-1a2b3c4d5e6fThe exec id from the started event.
Request Body
datastring optionalExample:
aGVsbG8KBase64 stdin bytes to append. Omit on an eof-only write.
offsetinteger requiredExample:
0Required. Count of stdin bytes already accepted. An equal offset appends. A lower offset retries and trims the overlap. A higher offset returns 409.
eofboolean optionalExample:
falseClose stdin after this write. A later write, or a second eof, returns 409.
Response Example
More Information
See /v2/harness-runtime/sessions/{session_id}/sandbox/exec/{exec_id}/stdin in the API reference for additional detail on responses, headers, parameters, and more.