Delete Approval

Database and access

These endpoints use the AgentOS-level database. Configure AgentOS(db=...) with an adapter that implements approvals; unsupported approval operations return 503. See Approvals.

Scoped callers can read only requester-owned records. Non-admin JWT callers are scoped with user isolation enabled; non-admin service-account PAT callers are scoped even without it. A caller-supplied user_id does not override this identity.

Delete a record

Deletion returns 204 and removes the approval record, not its associated run. Scoped callers cannot delete even their own approval records (the route returns 404). Unscoped callers retain write access under the deployment's authentication and permission configuration.

DELETE/approvals/{approval_id}

Authorization

HTTPBearer
AuthorizationBearer <token>

In: header

Path Parameters

approval_id*Approval Id

Response Body

application/json

curl --request DELETE 'https://example.com/approvals/string'
Empty