Resolve an authorization approval

POST/v1/authorization/approvals/{approvalId}/resolve

Atomically 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
NameLocationTypeRequiredDescription
approvalIdpathstringYes
Query parameters
None.
Header parameters
NameLocationTypeRequiredDescription
X-Computer-Agents-OrganizationheaderstringNoActive organization context. If omitted, the authenticated user's personal organization is used.

Body schema

Content type: application/json · Required

FieldTypeRequiredDescription
statusapproved | denied | cancelledYesCurrent lifecycle status.
reasonstringNo

What the API returns

Each response code below includes the documented payload shape for the ACP API.

200Resolved approvalapplication/json
FieldTypeRequiredDescription
dataobjectYes
data.idstringYesUnique identifier.
data.organizationIdstringYes
data.delegationIdstringNo
data.principalKindhuman | agent | service | systemYes
data.principalIdstringYes
data.actionIdstringYes
data.resourceTypestringYes
data.resourceIdstringYes
data.statuspending | approved | denied | expired | cancelledYesCurrent lifecycle status.
data.idempotencyKeystringNo
data.requestedAtstringNo
data.expiresAtstringYes
data.resolvedAtstringNo
data.resolvedByUserIdstringNo
data.resolutionReasonstringNo
409Approval is no longer pending
None.
Resolve an authorization approval
Loading...
Response 200
Loading...
See the ACP quickstart and SDK flow