FruxonDocs
AgentsApprovals

Lists the immutable audit timeline for a single approval request, newest-first.

Each entry records one lifecycle transition (requested / responded / cancelled / expired) with the actor, the channel they acted through (web, connector, topic callback, system), and — for the decision — the verdict and any free text. The requested entry also carries the tool parameters that were put up for approval. Returns an empty page when the approval id does not belong to the agent in the route.

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

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.

pendingApproval*string

The approval request ID whose timeline to read.

Formatuuid
tenant*string

The tenant identifier

Query Parameters

PageSize?integer

The maximum number of items to return per page

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/497f6eca-6276-4993-bfeb-53cbbbba6f08/auditEvents"
{
  "items": [
    {
      "id": "00000000-0000-0000-0000-000000000000",
      "approvalRequestId": "00000000-0000-0000-0000-000000000000",
      "agentId": "string",
      "sessionId": "string",
      "taskQueueId": 0,
      "toolKey": "string",
      "gateType": "TOOL_FLOW_STEP",
      "eventType": "REQUESTED",
      "channel": "WEB",
      "actor": "string",
      "decision": "APPROVE",
      "responseText": "string",
      "proposedParameters": {},
      "detail": "string",
      "correlationId": "string",
      "createdAt": 0
    }
  ],
  "nextPageToken": "string",
  "totalCount": 0
}
Empty
Empty
{
  "type": "string",
  "title": "string",
  "status": 0,
  "detail": "string",
  "instance": "string",
  "property1": null,
  "property2": null
}

Creates or updates the budget configuration for an agent

Upserts a single cap in place, identified by (origin, environment, period) — the same call creates the cap if none exists or replaces the existing one. The window is taken from `period` in the body (default `MONTHLY`); several caps on different windows can coexist on one bucket and all enforce together. Once a cap is set, the execution engine rejects new runs that would push that window's accumulated cost above it, and alert thresholds fire notifications as usage crosses them. The mandatory agent-wide daily, weekly, and monthly caps (on Production and Test) cannot be removed — set `enforceLimit: false` for a notify-only cap instead; optional caps can be removed via M:Fruxon.Server.Controllers.AgentBudgetController.Delete(System.String,Fruxon.Model.AgentSessions.ExecutionOrigin,System.String,Fruxon.Model.AgentBudgets.BudgetPeriod).

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/{pendingApproval}:respond` to resume them.