task-started
After the client sends the run-task command, the server returns a task-started event to signal that the task has started. The client can send subsequent commands only after receiving this event.
| Parameter | Type | Description |
|---|---|---|
| header.task_id | string | The task ID generated by the client. |
| header.event | string | Event type. Fixed value: task-started. |
| payload | object | Empty object. |
result-generated
After the client sends text, the server continuously returns result-generated events. Each event carries sentence-level metadata.
task-finished
The server returns a task-finished event when the task completes. The client can then close the WebSocket connection or reuse it to start a new task.
| Parameter | Type | Description |
|---|---|---|
| header.event | string | Event type. Fixed value: task-finished. |
| payload.usage | object | The fields are the same as usage in result-generated. |
task-failed
The server returns a task-failed event when the task fails. On receiving this event, the client must close the WebSocket connection and handle the error.
| Parameter | Type | Description |
|---|---|---|
| header.event | string | Event type. Fixed value: task-failed. |
| header.error_code | string | Error code. |
| header.error_message | string | Detailed error message. |