Skip to main content
Use this guide when Conversation view is empty or does not show the turns you expect. Check the recorded model event first, then inspect the history and reply fields that Conversation view reads.

​
Minimum data for a conversation

The POST /v1/events API requires event_type and an inputs object. Those fields make a valid event, but they do not guarantee a conversation can be displayed. Conversation view needs readable user or assistant content attached to the session you opened. To display a complete exchange, record both a user message and an assistant reply. For a model event that records one exchange, include: The user message and reply can be in one model event: put the user message in inputs.chat_history and the recorded reply in outputs.content. Include earlier assistant messages in chat_history when they are part of the recorded context. This example uses the HoneyHive CLI to create a session, capture its ID, and post one model event. Install the CLI and configure HH_PROJECT_API_KEY first. Set HH_DATA_PLANE_URL only when you use a non-default Data Plane URL. See the CLI getting started guide, session commands, and event commands for setup and options.
The API generates event_id when you omit it. If you omit parent_id, it defaults to session_id, so the event is attached directly to the session. After the minimum works, you can add optional timestamps, a model name, token counts, and nested events to provide more trace detail.

​
Troubleshoot the message shown in the UI

​
Common instrumentation mistakes

If you omit session_id, ingestion creates a new session for the event, so the event does not appear in the session you opened. Manual POST /v1/events requests do not convert inputs.messages or outputs.choices into the conversation fields. Put message objects in inputs.chat_history and the recorded assistant reply in outputs.content. A serialized history string in place of the inputs.chat_history array, messages without roles, empty content, or a history made only of system or tool messages does not provide visible conversation turns. System prompts and tool results can still be useful in the trace, but they do not replace a readable user or assistant turn. Check all chain events when model histories look correct. If any chain event in the session has an inputs.chat_history array, even an empty one, Conversation view reads turns from chain histories and recorded replies and ignores model event histories throughout the session. A chain with chat_history: [] and no readable reply can therefore prevent a conversation from displaying even when readable model events sit beside it. Correct that history or remove it from the chain. For the full view behavior, see Thread View. For manual event ingestion, see Tracing via API.