Skip to main content
POST
Queue a follow-up after the active runtime turn

Authorizations

Authorization
string
header
required

Runtime context-key (rctx_*) issued by the Ravi gateway. Used by ordinary gateway operations; not accepted by Console-only operations. Bootstrap the first key with ravi daemon init-admin-key; rotate, derive, and revoke via the ravi context family. Specs: runtime/context-keys, sdk/auth.

Body

application/json
session
string
required

Ravi session name or key

text
string
required

Follow-up text to run after the active turn

execute
boolean

Actually queue the follow-up; default is a dry-run that only shows the plan (exit 3)

expectedTurn
string

Expected active runtime turn id

thread
string

Expected runtime thread id

turn
string

Runtime turn id

Response

Success — body conforms to the @Returns schema.

ok
boolean
required
data
any
error
string
operation
string
{key}
any