Execute one credential-fenced durable run resume
POST
/v1/threads/{threadId}/runs/{runId}/resume-dispatchInternal workload boundary used only by a lease-bound thread_resume dispatch credential for the exact thread and parked run. The runtime restores the verified checkpoint into a canonical child run and applies the pending control idempotently.
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 |
| runId | 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.
200Resume applied or an idempotent prior child run returnedapplication/json
None.
403Workload credential is not fenced to this dispatch
None.
409Run is not parked or lacks a verified pending checkpoint
None.
Execute one credential-fenced durable run resume
Loading...
Response 200
Loading...