Section ID:
DOC-API-MODEL-schema-po1qsocerv#overview
LLMMessagePublishedEvent
Domain event published when a new assistant/tool message is produced.
Meaning and usage
Section ID: DOC-API-MODEL-schema-po1qsocerv#meaning
See the definition above.
Usage profiles
Section ID: DOC-API-MODEL-schema-po1qsocerv#fields
| Usage | Fields and validation |
|---|---|
| In requests | View fields |
| In responses | View fields |
In requests
Section ID: DOC-API-MODEL-schema-po1qsocerv#request
API JSON uses JSON field names (camelCase).
| Field | Type | Presence | Meaning |
|---|---|---|---|
Section ID: DOC-API-MODEL-schema-po1qsocerv#request-field-messagemessage | Message | Optional | The generated assistant/tool message |
In responses
Section ID: DOC-API-MODEL-schema-po1qsocerv#response
API JSON uses JSON field names (camelCase).
| Field | Type | Presence | Meaning |
|---|---|---|---|
Section ID: DOC-API-MODEL-schema-po1qsocerv#field-messageSection ID: DOC-API-MODEL-schema-po1qsocerv#response-field-messagemessage | Message | Optional | The generated assistant/tool message |
Examples
Section ID: DOC-API-MODEL-schema-po1qsocerv#examples
event-llm-message-published
Section ID: DOC-API-MODEL-schema-po1qsocerv#example-event-llm-message-published
Illustrative payload, not a captured delivery. Identifiers, tool names and outcomes are examples; omitted fields depend on the event.
{
"message": {
"role": "ROLE_ASSISTANT",
"content": [
{
"type": "CONTENT_PART_TYPE_TEXT",
"content": "Here is your daily briefing."
}
],
"messageId": "924ad207-f757-4b1f-bf41-8344ce32dd01",
"sequence": "2",
"generatedBy": "9d4c2e1f-27b1-4304-ae54-af7fe876df31"
}
}
Download the public reference contract.
Document ID: DOC-API-MODEL-schema-po1qsocerv