Skip to main content
Report activity that isn’t a message: a user started or stopped typing, or edited a message. These events feed behavioural signals, which sharpen the speak/stay-silent decision and surface turn_taking.signal events (for example, detecting that a user has been typing without sending). You only need this when the thread enables behavioural signals. A sent message is reported through submit_messages, not here. This call is not billable.

Authorization

string
required
Your bearer token: Bearer <token>. See Authentication.

Request body

string
required
The thread the event happened in.
string
required
The kind of event: typing_start, typing_stop, or message_edited.
string
required
Who produced the event — the person’s id, 1–255 characters.
string
Optional client-measured time of the event (ISO 8601). Improves the timing of behavioural signals; falls back to server receipt time when omitted.
Request

Response

string[]
Any behavioural tags the event produced. Empty for typing and edit events today.
200 OK

Errors

See Errors for the envelope shape.

Example