Append a message without generating

POST 
/api/v1/llm/append-message

Appends a context message to the thread's history without starting generation for this call. Use it to record a system note, an external event or other context that later generations should see without triggering a reply.

Read conversation-state to confirm the event: append assigns the next monotonic sequence immediately and publishes a message event. ROLE_USER opens a new user turn; other roles join the most recent user turn. Choose the role for how the event should appear in history, without changing the fact it records.

Append bypasses the interrupt policy and pending queue. It can run while another turn is active, but that turn may already have assembled its provider request. This call does not stop already running work or guarantee zero account-level cost: storage and future model input can still cost money.

The following access conditions are preserved as declared intent and are not implemented by generated code: Authorized scoped domain action.

Use this in a guide: Get a customer’s reply and recover an interrupted send · Context and compaction

Request

Responses

200

Message appended

Schema-valid request illustration; replace example identifiers and confirm operation prerequisites.

Section ID: DOC-MA-conversations-api-appendMessage#example-conversations-appendMessage-request

Request example

{
  "conversationKey": "example_123",
  "message": {
    "role": "ROLE_USER",
    "content": [
      {
        "type": "CONTENT_PART_TYPE_TEXT",
        "content": "Hello"
      }
    ]
  }
}

Guide request for Separate recipe: record an onboarding event without another reply. Replace example resource identifiers with your own authorized values.

Section ID: DOC-MA-conversations-api-appendMessage#example-cookbook-managed-agents-conversations-generation-04-request

Request example

{
  "conversationKey": "b81d5345-c1f9-4fb9-b558-a6327c75b842",
  "message": {
    "role": "ROLE_USER",
    "content": [
      {
        "type": "CONTENT_PART_TYPE_TEXT",
        "content": "CONTEXT UPDATE: user completed onboarding."
      }
    ]
  }
}

Illustrative response shape; omitted default fields and actual outcomes depend on the operation.

Section ID: DOC-MA-conversations-api-appendMessage#example-conversations-appendMessage-response

Response example

{}

Document ID: DOC-MA-conversations-api-appendMessage. Section identities and revisions.

Section	Stable reference
Append a message without generating	DOC-MA-conversations-api-appendMessage#overview
Request	DOC-MA-conversations-api-appendMessage#request
Responses	DOC-MA-conversations-api-appendMessage#responses