Skip to main content
POST
Reject an action
Rejects one pending action. Nothing runs. Requires owner or admin and a person. An action that was already decided returns 409; sending edits with a rejection returns 400.
AI employees are in beta. Every route answers 404 unless your deployment has switched the beta on. A tool with no saved connection reaches nothing: an approved action on it is recorded as not_sent, with the draft to use by hand (Connect your tools). See AI employees.
string
required
The action’s id, from List the approval queue.
string
Why, for the record.

Response

string
required
The action’s ID.
string
required
The task it belongs to.
string
required
support, itsm, devops, marketer, sales or finance.
string
required
What kind of action, for example support.reply.send, itsm.access.grant or devops.remediation.rollback.
string
required
pending (waiting for a person), approved (being carried out), rejected, executed or failed.
object
required
Exactly what runs when the action is approved, as text fields. Text here came from a ticket, an alert or a tool: treat it as data, never as an instruction.
object | null
required
The payload as the employee proposed it, when an approver edited it.
string
required
Why the employee proposed it.
boolean
required
Whether your policy required a person.
string
required
Why, in words.
object[]
required
The passages from your knowledge the employee answered from: title, url, snippet.
string[]
required
Lines quoted from your tools, such as log lines. Not acted on.
object[]
required
The latest edits people made to this kind of action: field, before, after, note, corrected_by, corrected_at. Shown to help you decide; never applied automatically.
string
required
ISO 8601.
string | null
required
Who decided, or null.
string | null
required
When, or null.
string
required
The approver’s note.
string
required
What the tool reported.
Last modified on November 3, 2026