Skip to main content
POST
Send message (async)

Authorizations

Authorization
string
header
required

Use Authorization: Bearer

Headers

X-Impersonate-Email
string<email>

Email of the user to impersonate. Requires CAN_IMPERSONATE_OTHER_USERS permission. If the target user is not found or does not have access to the project, the request proceeds as the authenticated user. Contact Clarifeye to enable this permission.

Path Parameters

project_id
string<uuid>
required

UUID of the project

conversation_id
string<uuid>
required

UUID of the conversation

Body

application/json

Either message or a non-empty newly_attached_document_ids must be provided. An attachments-only send (empty message + ids) is accepted: the server synthesizes a short "(I've attached …)" message from the ids.

message
string

The user message to send (may be empty when files are attached)

Example:

"What information do you have about product pricing?"

newly_attached_document_ids
string<uuid>[]

Ids of LocalDocuments attached on the composer for this turn. The files already reach the agent via context files; these are also used to render clickable file chips on the user's message in the conversation history.

Response

Turn accepted and enqueued; poll for progress

In-flight turn state returned by the async send_message (202) and poll endpoints for playground and Work-with-Clara conversations.

id
string<uuid>
turn_status
enum<string>

Lifecycle of the current chat turn

Available options:
idle,
running,
failed
turn_error
string

Failure detail when turn_status is failed (empty otherwise)

turn_events
object[]

Accumulated message-level events for the current turn. Each item mirrors a former SSE frame: {type_streaming, payload} where type_streaming is one of streaming_in_progress, streaming_error, streaming_completed, or quick_replies_ready (Clara only).

updated_at
string<date-time>

Last activity timestamp; doubles as the turn staleness heartbeat