Skip to main content
POST

Authorizations

Authorization
string
header
required

Workspace API key created in Erstan Settings. Keys carry scopes (agents:list, agents:read, agents:write, agents:run, runs:read, tasks:execute, documents:read, documents:write, files:read, files:write). Agent access follows the key creator's current workspace, team, and agent permissions. Agent draft creation requires agents:write; update, validation, and publishing require both agents:read and agents:write; draft testing also requires agents:run. Keys with tasks:execute must include at least one allowed project or team (allowedProjectIds / allowedTeamIds); keys with document or file scopes must include at least one allowed team. Empty allowlists mean no access — the API fails closed.

Path Parameters

runId
string<uuid>
required

Waiting run ID returned by POST /v1/public/agents/{agentId}/runs.

Body

application/json
interactionId
string
required

Exact value from the current get_run pendingInteraction.

Required string length: 1 - 512
message
string
required

Free-text response; maps to the sole question when exactly one exists.

userMessage
string

User-facing transcript text and free-text response alias.

answers
object

Answers keyed by question ID for structured or multi-question interactions.

answerLabels
object
questionIds
string[]
action
enum<string>
Available options:
submit,
skip
skip
boolean
skipped
boolean

Response

Reply accepted and the run queued to resume.

runId
string<uuid>
required
agentId
string
required
status
string
required
Allowed value: "running"