Post a follow-up event to a session
Requires sessions:write. The message is authored by the key itself (author.type: "api_key") — a key may never author as anyone else. The agent_id field is accepted but ignored for a key, so a key cannot switch which agent answers mid-conversation; start a new session instead. A key converses only in the chat sessions it initiated — posting into any other session (another key’s chat, a person’s chat, a trigger session) is 404.
Authorizations
Account API key: key id as the username, secret as the password.
Path Parameters
Body
Response
Successful response
- Option 1
- Option 2
- Option 3
- Option 4
- Option 5
- Option 6
- Option 7
- Option 8
- Option 9
- Option 10
- Option 11
- Option 12
- Option 13
- Option 14
- Option 15
- Option 16
- Option 17
- Option 18
- Option 19
- Option 20
Severity of the line: INFO for ordinary output, ERROR for error-level output. Nullable for now; pre-existing rows have no level.
INFO, ERROR When the line was produced in the container (not received)