Events

While a session runs, its results reach your systems two ways. Both carry the same operator results — pick whichever fits how you want to consume them, or use both.

• Session events — a realtime stream you hold open for the life of the call. You receive every operator result (and, optionally, transcript turns) as it is produced. Best for live dashboards and in-call UX.
• Webhooks — HTTP callbacks the platform pushes to your endpoint when a result meets a condition you defined in the configuration. Best for triggering downstream systems without holding a connection open.

The stream delivers everything; webhooks deliver only what your actions select.

Ignore fields you don't recognise. Event and webhook payloads document a stable set of fields, but a payload may also carry additional internal or usage fields that are not part of the contract and may change or disappear without notice. Read the fields you need by name and ignore the rest.