List the human-in-the-loop (HITL) events for a conversation. When Fin is unsure of an answer it can consult a teammate before replying, proposing a draft that the teammate approves, steers with free-text feedback, or takes over. Each consultation is returned as a series of events, oldest first, across every consultation on the conversation.

Requires the read_conversations OAuth scope, and the caller must be able to access the conversation.

Events are only recorded once a consultation has ended, so a consultation still awaiting a teammate does not appear.

Which fields appear in data depends on event_type:

A consultation always produces a fin_consultation_started and a fin_consultation_finished event. fin_draft_proposed appears when Fin proposed a draft. fin_teammate_input_received appears once per round of teammate feedback, and fin_draft_revised once per round where Fin produced a revised draft in response.

Notes on interpreting the response:

• hitl_cycle_id identifies the consultation, so it is the same on every event of one consultation. It is not unique per event. A conversation can hold several consultations — a consultation that replaces an outstanding one finishes with an outcome of superseded.
• conversation_part_id links an event to a conversation part where one exists. It is null in ordinary cases: teammate feedback given through the inbox creates no conversation part, a revised draft has no part of its own, and a consultation that escalated or was superseded sent no reply.
• created_at on fin_draft_proposed is approximate. It reports when the consultation started, which is when the draft was proposed.
• rule_id, rule_name and rule_threshold_percent are recorded when the consultation begins and are not updated afterwards, so a rule that has since been renamed or retuned will not match its current settings. They are null for consultations not triggered by a rule.
• reviewer_admin_id identifies the teammate involved in that event: on fin_teammate_input_received the teammate who gave the feedback, and on fin_consultation_finished the teammate who approved the draft or took over. On a consultation with several rounds these can be different teammates.
• rounds_count counts every round of teammate feedback the consultation had. Only the ten most recent rounds are retained, so a heavily steered consultation returns fewer fin_teammate_input_received events than rounds_count.
• Redacting a conversation removes this data. Depending on how it was redacted, the conversation either returns no events or returns events whose text fields are all null.