Skip to main content
POST/api/public/v1/sessions/{id}/handoff/resume

sessions.handoff_resume

sessions.handoff_resume — Return control only after human verification and signed worker readback.

Capability: session.controlCommand (idempotent)MCP tool: sessions_handoff_resume
View as Markdown

Parameters

NameTypeRequiredDescription
idpathstring (uuid)Yes
command_idbodystring (uuid)Yes
idempotency_keybodystringYes(min length 1, max length 163)
epochbodyintegerYes(min 0, max 9007199254740991)

Examples

curl -X POST "https://browlix.com/api/public/v1/sessions/<id>/handoff/resume" \
  -H "Authorization: Bearer $BROWLIX_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"command_id":"<uuid>","idempotency_key":"<idempotency_key>","epoch":0}'

Response

201 with { data, replayed: false, correlation_id } the first time; 200 with replayed: true when the same command_id and body come again.

The field list of this reply is not published yet; read data as JSON.

Errors

CodeHTTPRetryable
UNAUTHENTICATED401No
FORBIDDEN403No
RATE_LIMITED429Yes
VALIDATION_FAILED422No
NOT_FOUND404No
CONFLICT409No
OUTCOME_UNKNOWN202Yes
DEPENDENCY_UNAVAILABLE503Yes
UNKNOWN500No

Every error code and when to retry

All operations

Using an AI agent?

Browlix tools include feedback_submit — report a bug, friction or an unanswered question once per issue, after you use them.

How feedback works