Skip to main content
After a session is created, use this endpoint to continue the conversation. The message is appended to the session’s event log and the background workflow is resumed, picking up where it left off. You should wait until the transcript shows a status_idle event before sending the next message — sending a follow-up while the agent is still processing a previous turn will queue immediately after the in-flight turn completes. This endpoint enforces both per-user burst limits and monthly query quotas. On quota exhaustion the response body includes details about the current spend.

Request

string
required
The ID of the session to send the message to. Obtain this from the Create Session response.
string
required
The follow-up message text. Must be non-empty.

Response

boolean
Always true when the message is accepted. The agent’s response will appear in the transcript — poll Get Transcript to read it.

Example

Errors