Skip to main content
POST
Answer, approve, cancel or retry a run

Authorizations

Authorization
string
header
required

An API key from your Devic console, sent as Authorization: Bearer <key>. An embedded front end sends a tenant-session token instead, so no API key reaches the browser, and an OAuth integration sends its access token. Missing, invalid or expired credentials get a 401. See Authentication.

Headers

X-Devic-User
string

Only with an API key: the userUID or email of a person of the key's account to act as, with that person's permissions. Without it, an API key acts as the account integration ("API"), which sees shared workspaces only. A person's token cannot name someone else.

Path Parameters

wid
string
required

Workspace id

tid
string
required

Thread id

runId
string
required

Invocation (run) id

action
enum<string>
required

The action

Available options:
answer,
approve,
cancel,
retry

Body

application/json

Depends on the action. answer: { revision, inputId, response: { answers: [{ id, selected?, other?, note? }] } } or { revision, inputId, skipped: true }. approve: { revision, actionId, always? }. cancel, retry: {}.

revision
integer
inputId
string
actionId
string
response
object
skipped
boolean
always
boolean

Response

Success — wrapped as { success: true, data }

success
boolean
Example:

true

data
object

A run of an assistant answering a message.