FruxonDocs
AgentsApprovals

Lists approval requests for the given agent, newest first

Each item represents one parked execution waiting on a human gate, including the prompt text shown to the approver, the tool call arguments under review, and the inbound channel (web, Telegram, Slack, …) the request was dispatched on. The default `Pending` filter is what an inbox UI wants; pass `Approved`, `Rejected`, or `Cancelled` to see history. Pair items in this list with `POST .../pendingApprovals/{approvalId}:respond` to resume them.

GET
/v1/tenants/{tenant}/agents/{agent}/pendingApprovals

Authorization

Bearer
AuthorizationBearer <token>

JWT Authorization header using the Bearer scheme. Enter 'Bearer' [space] and then your token.

In: header

Path Parameters

agent*string

The unique identifier of the agent.

tenant*string

The tenant identifier

Query Parameters

status?string

Filter by lifecycle state. Defaults to Fruxon.Model.HumanApprovalRequests.HumanApprovalStatus.Pending.

Value in"UNSPECIFIED" | "PENDING" | "RESPONDED" | "CANCELLED" | "EXPIRED"
PageSize?integer
Formatint32
PageToken.Skip?integer
Formatint32
PageToken.Cursor?string

Opaque cursor token from an external system (e.g. RAG API). When set, M:Fruxon.Common.Collections.PageToken.AsString returns this value directly instead of encoding Fruxon.Common.Collections.PageToken.Skip.

Response Body

curl -X GET "https://api.fruxon.com/v1/tenants/string/agents/string/pendingApprovals"
{
  "items": [
    {
      "id": "00000000-0000-0000-0000-000000000000",
      "agentId": "string",
      "agentRevision": 0,
      "flow": "string",
      "sessionId": "string",
      "taskQueueId": 0,
      "executionRecordId": "00000000-0000-0000-0000-000000000000",
      "gateType": "TOOL_FLOW_STEP",
      "stepIdentifier": "string",
      "toolCallId": "string",
      "toolKey": "string",
      "outboundMessage": "string",
      "proposedParameters": {},
      "authorizedApprovers": [
        "string"
      ],
      "deliveryRoute": {
        "id": "00000000-0000-0000-0000-000000000000",
        "connectorId": "00000000-0000-0000-0000-000000000000",
        "provider": "string",
        "parameters": null
      },
      "deliveryMessageId": "string",
      "correlationToken": "string",
      "status": "PENDING",
      "expiresAt": 0,
      "respondedAt": 0,
      "respondedBy": "string",
      "decision": "APPROVE",
      "responseText": "string",
      "createdAt": 0,
      "modifiedAt": 0
    }
  ],
  "nextPageToken": "string",
  "totalCount": 0
}
Empty
Empty
{
  "type": "string",
  "title": "string",
  "status": 0,
  "detail": "string",
  "instance": "string",
  "property1": null,
  "property2": null
}

Requests access to an agent.

Creates a pending access request and notifies agent admins via email.

Cancels a pending request without resuming the execution

Use this when an operator wants to abandon a parked execution rather than approve or reject — for example, when the request has gone stale or was triggered by a bad input. The execution is finalized as Failed with the supplied reason recorded on the trace, so downstream metrics and alerts treat it as a non-completion rather than a rejection. Returns 409 if the request has already been responded to or cancelled; in that case the existing terminal state is authoritative.