How embedded chat works with Whop
Whop hosts the messages, realtime updates, media uploads and moderation. You mint a short-lived token for each of your own users and drop in one element. There is no chat database to run and no websockets to manage.
On the right is Orbit, a small community app, rendered two ways. The Prebuilt embed tab is Whop's drop-in <ChatElement>, live on a production company. The Chat API tab renders the same kind of conversation from plain REST, on sandbox, with a UI you control. Toggle between them above the chat.
The embed is fully interactive: switch profiles and post for real. It is heavily moderated and resets periodically. In the Chat API tab, the messages you type are simulated locally so the shared sandbox channels stay clean.
The Chat API tab runs on Whop's sandbox; the Prebuilt embed runs on a separate production company.
Companion demo for the article on adding embedded chats with Whop.
Ava, Ben and Cara are connected accounts created with companies.create. Switch between them here: each acts through its own short-lived, company-scoped token, minted server-side for every call. The embed tab fetches its token from /api/chat/prod-token; the Chat API tab mints one inside its message routes.