dots.v2.agents.sessions.bySession_id().hitl.byRequest_id().post()
Generated on 13 Nov 2026
from DoTs version
v1.24.0
Usage
client.v2.agents.sessions.bySession_id(session_id).hitl.byRequest_id(request_id).post(body: Resolve_hitl_request, requestConfiguration?: RequestConfiguration<object>): Promise<void>Description
harness-api forwards the decision into the owning microVM via the inbound runtime.v1.OHR.ResolveHITL RPC (dialed through the guest-fronting proxy), which unblocks the gated agent action. The resolution is also echoed to all attached clients as a HITLResolved event on StreamSession. Returns 204 No Content on success.
Parameters
Path Parameters
session_idstring requiredExample:
a1b2c3d4-e5f6-7890-abcd-ef1234567890The session UUID.
request_idstring requiredExample:
hitl_exampleThe HITL request identifier.
Headers
X-Device-UUIDstring optionalExample:
device-uuid-exampleOptional hardware device id forwarded by doctl. Recorded on the resulting HITL decision.
Request Body
outcomestring requiredHITLOutcome is the user's decision on a HITL request. DEFER backs off this attempt without treating it as a rejection.
reasonstring optionalExample:
exampleOptional free-text reason. Captured in the audit trail; not interpreted.
sourcestring optionalHow a HITL resolution was triggered. Defaults to RESOLUTION_SOURCE_OUT_OF_BAND when omitted.
Request Sample
More Information
See /v2/agents/sessions/{session_id}/hitl/{request_id} in the API reference for additional detail on responses, headers, parameters, and more.