Continue a thread after a durable permission decision
POST
/v1/threads/{threadId}/permission-continuations/{approvalId}/executeInternal handoff for a lease-bound thread_permission_resume workload credential. The exact thread, approval, actor, organization and current claim must match. The saved action receives at most one continuation grant after current policy is rechecked.
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 |
| approvalId | path | string | Yes | — |
Query parameters
None.
Body schema
Content type: application/json · Required
| Field | Type | Required | Description |
|---|---|---|---|
| dispatchId | string | Yes | — |
What the API returns
Each response code below includes the documented payload shape for the ACP API.
200Continuation delivered, blocked, or already handed offapplication/json
None.
403Workload credential or dispatch lease does not match
None.
404Thread or permission checkpoint not found
None.
409The original worker or another continuation owns the handoff
None.
Continue a thread after a durable permission decision
Loading...
Response 200
Loading...