Decide a pending permission request
POST
/v1/threads/{threadId}/permission-requests/{requestId}/decisionApprove or deny a live or persisted runtime permission request for this thread.
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 |
|---|---|---|---|---|
| threadId | path | string | Yes | Thread ID |
| requestId | path | string | Yes | — |
Query parameters
None.
Body schema
Content type: application/json · Required
| Field | Type | Required | Description |
|---|---|---|---|
| decision | allow | deny | Yes | — |
| reason | string | No | — |
What the API returns
Each response code below includes the documented payload shape for the ACP API.
200Permission decision acceptedapplication/json
| Field | Type | Required | Description |
|---|---|---|---|
| ok | boolean | Yes | — |
| requestId | string | Yes | — |
| decision | allow | deny | Yes | — |
| active | boolean | No | Whether the decision was delivered to a live waiting runtime session. |
| message | string | No | Message text. |
404Thread or permission request not found
None.
Decide a pending permission request
Loading...
Response 200
Loading...