Resolve an authorization approval
POST
/v1/authorization/approvals/{approvalId}/resolveAtomically resolves a pending approval as the resource owner or an organization administrator.
How to call this endpoint
Every ACP API request uses bearer authentication. The examples here show the actual request path, auth header, and body shape that the platform expects.
Path, query, and header parameters
These parameters control which ACP object the endpoint acts on and how the request is processed.
Path parameters
| Name | Location | Type | Required | Description |
|---|---|---|---|---|
| approvalId | path | string | Yes | — |
Query parameters
None.
Header parameters
| Name | Location | Type | Required | Description |
|---|---|---|---|---|
| X-Computer-Agents-Organization | header | string | No | Active organization context. If omitted, the authenticated user's personal organization is used. |
Body schema
Content type: application/json · Required
| Field | Type | Required | Description |
|---|---|---|---|
| status | approved | denied | cancelled | Yes | Current lifecycle status. |
| reason | string | No | — |
What the API returns
Each response code below includes the documented payload shape for the ACP API.
200Resolved approvalapplication/json
| Field | Type | Required | Description |
|---|---|---|---|
| data | object | Yes | — |
| data.id | string | Yes | Unique identifier. |
| data.organizationId | string | Yes | — |
| data.delegationId | string | No | — |
| data.principalKind | human | agent | service | system | Yes | — |
| data.principalId | string | Yes | — |
| data.actionId | string | Yes | — |
| data.resourceType | string | Yes | — |
| data.resourceId | string | Yes | — |
| data.status | pending | approved | denied | expired | cancelled | Yes | Current lifecycle status. |
| data.idempotencyKey | string | No | — |
| data.requestedAt | string | No | — |
| data.expiresAt | string | Yes | Null while a human runtime approval is pending without a deadline. Resolution starts a bounded grant lifetime; a null expiry never authorizes execution. |
| data.resolvedAt | string | No | — |
| data.resolvedByUserId | string | No | — |
| data.resolutionReason | string | No | — |
409Approval is no longer pending
None.
Resolve an authorization approval
Loading...
Response 200
Loading...