The visitor is (or stopped) typing

POST 
/api/widget/typing

PUBLIC endpoint (anonymous visitors, NO staff auth). Tells the agents that the visitor is typing in their OWN conversation (taken EXCLUSIVELY from the verified session token). Only a boolean is sent, never a preview of the text. Broadcast to the staff conversation channel as a typing event with actor_kind: contact.

The web widget is the only channel that reports customer typing: WhatsApp, Messenger, Instagram and Telegram deliver no inbound typing signal. Starts are coalesced per conversation (at most one every ~2 s); a stop is always forwarded. Rate-limited on its own bucket so typing never spends the messaging budget.

Request

Responses

202

Accepted (no body).

403

Missing / invalid / cross-tenant session token.

404

Unknown or missing widget_key, or the conversation is gone.

422

The request failed validation.

429

Rate limit exceeded.

Response Headers

X-RateLimit-Limit

Request quota for the current window.

X-RateLimit-Remaining

Remaining requests in the current window.

Retry-After

Seconds to wait before retrying.