Queue a steering message for a run
POST
/v1/threads/{threadId}/runs/{runId}/steeringRecord checkpoint or interrupt delivery intent. A future durable run coordinator consumes the queued delivery; this endpoint does not claim immediate runtime delivery.
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 |
|---|---|---|---|
| content | string | Yes | Raw text content. |
| mode | checkpoint | interrupt | No | — |
| intent | string | No | — |
| reason | string | No | — |
| idempotencyKey | string | No | — |
| clientMessageId | string | No | — |
What the API returns
Each response code below includes the documented payload shape for the ACP API.
202Steering delivery queued for a coordinatorapplication/json
None.
409The explicitly targeted run is already terminal
None.
Queue a steering message for a run
Loading...
Response 202
Loading...