Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.whop.com/llms.txt

Use this file to discover all available pages before exploring further.

Direct messages are private conversations between two or more users. Use them when your app already has users and you want private messaging inside your product. For embedded chat, DMs belong to your company context by default. That means users only see conversations created for your app, not unrelated Whop messages.

When to use direct messages

Use direct messages when the conversation should be limited to specific members. Examples:
  • Buyer-to-seller messaging inside your app
  • A private coaching thread between a coach and client
  • A small group conversation for a project, cohort, or team
  • A marketplace conversation between two matched users
  • User-to-user messaging inside your app

What makes DMs different

DMs are the chat type for private conversations between specific users.
  • They can be one-on-one or group conversations with up to 50 members.
  • Only the users added as members can see and participate in the conversation.
  • They appear in the DMs list element, so users can browse and open their recent conversations.
  • They can be scoped to your company, giving your embedded app its own inbox separate from unrelated Whop messages.
  • They support custom conversation names and member management.

Constraints

  • DMs do not grant access based on product membership. Add or remove members directly when access changes.
  • DMs do not have admin-only, read-only, or room-level moderation controls. Use channels for moderated rooms.
  • DMs do not include a support inbox or open/resolved workflow. Use support chats for customer support.
  • DMs are not designed for large communities, announcements, or member-wide rooms. Use channels for that.

Access model

Each DM has members. Those members are the only users who can see and participate in the conversation. When you create DMs for embedded chat, keep them tied to your company. This gives your app its own inbox and keeps conversations separate from the rest of Whop.
DM channel IDs start with feed_.

Set up a direct message

1

Sync or create users

Make sure every participant has a Whop user ID. If your app has its own users, map them to Whop users first. See Sync your users.
2

Create the DM channel

Use Create DM Channel to create the conversation with its initial members.
3

Add more members when needed

Use Create DM Member to add a user to an existing DM. Use Delete DM Member to remove one.
4

Render the conversation or list

Use the Chat element for a single DM, or the DMs list element to let users pick from their conversations.
Then render the DM with the returned channel ID:
<ChatElement
  options={{ channelId: "feed_XXXXXXXXXXXXXX" }}
  style={{ height: "100dvh", width: "100%" }}
/>

Manage direct messages

Use List DM Channels, Update DM Channel, and Delete DM Channel to manage conversations. Use List DM Members, Create DM Member, and Delete DM Member to manage participants.
If you use the DMs list element, keep it tied to your company so users only see conversations for your embedded chat experience.

Next steps

DMs list element

Show DM conversations and handle channel selection.

Sync your users

Create or map Whop users before creating DM channels.