List held actions waiting for (or decided by) a person

GET

https://api.jelliu.co/api/agent-approvals

GET

/api/agent-approvals

curl https://api.jelliu.co/api/agent-approvals \
     -H "Authorization: Bearer <token>"

{
  "data": [
    {
      "id": "3f2a9c1e-5b7d-4e8a-9c6b-1d2e3f4a5b6c",
      "summary": "Crear nota en HubSpot (Ana Gómez)",
      "tool_name": "HUBSPOT_CREATE_NOTE",
      "tool_source": "composio",
      "expires_at": "2026-09-23T16:00:00Z",
      "status": "pending",
      "executable": true,
      "execution_note": "Aprobar la ejecuta una sola vez, tal como la pidió el agente. También se puede aprobar sin ejecutar.",
      "agent_id": "8b1c2d3e-4f5a-4b6c-8d7e-9f0a1b2c3d4e",
      "agent_name_at_time": "Cobros",
      "conversation_id": "1a2b3c4d-5e6f-4a7b-8c9d-0e1f2a3b4c5d",
      "call_id": null,
      "toolkit": "hubspot",
      "reversibility": "reversible",
      "matched_rule": "tool",
      "params": {
        "hs_note_body": "[REDACTED]"
      },
      "requested_at": "2026-09-23T15:00:00Z",
      "expired_by_clock": false,
      "decided_by": null,
      "decided_at": null,
      "decision_note": null,
      "executed_at": null,
      "execution_action_id": null,
      "execution_error": null
    }
  ]
}

The approval tray: writes an agent asked for that the workspace’s approval policy held, and actions the platform itself holds for a person (registering a confirmed payment in the ERP). Newest first. The clocks are applied on read: a pending row past expires_at is returned as expired, and an executing row stuck for more than 10 minutes as execution_unknown.

Every row held since 2026-09-23 carries summary, the request as one Spanish sentence (“Crear nota en HubSpot (Ana Gómez)”, “Registrar pago de $ 150.000 COP de Juan Pérez en Alegra, aplicado a la factura FV-120. …”). It is built from the tool, its app and the person the conversation serves — never from the arguments. Older rows have summary: null. params are the arguments, redacted. The raw arguments are never returned.

Access

Required role: admin (a person, or a key with full scope).
Rate limit: Audit routes limit. See Rate limits.
Plan: Available on every plan.

Authentication

AuthorizationBearer

Workspace API key: jl_ followed by 64 lowercase hex characters, created by the workspace owner in the dashboard (Settings → API Keys) and sent as Authorization: Bearer jl_.... The plaintext is shown once, at creation; Jelliu stores only a SHA-256 hash. A workspace can hold up to 25 active keys.

Scope	GET / HEAD	POST / PUT / PATCH / DELETE	Admin-only routes
`read`	Yes	No	No
`write`	Yes	Yes	No
`full`	Yes	Yes	Yes

Operations restricted to admins or owners reject keys without the full scope with 403, and say so in their description. No key, whatever its scope, can mint or revoke API keys or rotate a webhook secret — that requires a signed-in owner session. A revoked key stops authenticating within about 10 seconds. See Authentication.

Query parameters

statusenumOptional

agentIdstringOptionalformat: "uuid"

limitintegerOptional1-200Defaults to 50

offsetintegerOptional>=0Defaults to 0

Response

The held actions.

datalist of objects

Errors

400

Bad Request Error