Limits and delivery

Limits

Messages are limited to 4,000 characters. Per browser IP and workspace, per minute: 10 conversations started, 30 messages sent, 60 configuration reads, and 60 conversation lists. Over the limit the SDK surfaces an error event and the underlying request answers HTTP 429; back off rather than retrying immediately.

Every request the SDK makes is checked against the workspace's origin allowlist, so a publishable token lifted from your HTML is useless from another page. The allowlist is what keeps a token on your own site; it is not evidence of who the visitor is. To tell the agent who is signed in, see Sessions and channels.

Reply style

replyStyle	Delivery
stream	Default on web: one complete reply, without artificial delay
paced	Short messages with typing indicators and pauses
instant	One complete reply with no typing events

stream is not token-by-token network streaming. Render the received reply progressively if desired. The style is fixed at chat creation; use fresh: true when changing it.

Use the SDK for realtime delivery. The underlying socket protocol is not a public integration contract.