Classify an activity message without persisting it
POST
/v1/threads/{threadId}/activity/classifyDeterministically preflight an attachment-free message so clients can choose the communicator activity endpoint, legacy worker follow-up queue, or legacy control path without creating duplicate messages, runs, or deliveries.
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 |
Query parameters
None.
Body schema
Content type: application/json · Required
| Field | Type | Required | Description |
|---|---|---|---|
| content | string | Yes | Raw text content. |
| runId | string | No | — |
| replyToRunId | string | No | — |
| mode | checkpoint | interrupt | fyi | No | — |
| targetType | string | No | — |
What the API returns
Each response code below includes the documented payload shape for the ACP API.
200Non-persisted routing classification and suggested transportapplication/json
None.
Classify an activity message without persisting it
Loading...
Response 200
Loading...