Append logs

POST/v1/threads/{threadId}/logs

Append direct logs to a thread for flows that bypass normal container execution.

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
NameLocationTypeRequiredDescription
threadIdpathstringYesThread ID
Query parameters
None.

Body schema

Content type: application/json · Required

FieldTypeRequiredDescription
logsobject[]Yes—
logs[].createdAtstringNoISO 8601 timestamp.
logs[].timestringNo—
logs[].messagestringNoMessage text.
logs[].typeinfo | error | success | warningNo—
logs[].eventTypestringNo—
logs[].isUserMessagebooleanNo—
logs[].isReasoningbooleanNo—
logs[].isActionSummarybooleanNo—
logs[].isPlanningbooleanNo—
logs[].isLLMResponsebooleanNo—
logs[].metadataobjectNoFree-form metadata object.

What the API returns

Each response code below includes the documented payload shape for the ACP API.

200Logs appendedapplication/json
FieldTypeRequiredDescription
successbooleanNoWhether the request succeeded.
logsAddedintegerNo—
Append logs
Loading...
Response 200
Loading...
See the ACP quickstart and SDK flow