Embedded Inbox

Overview

Embedded Inbox is a ready-to-use messaging UI for sending and receiving messages from your own product. It is loaded in the browser and does not require a separate API request for each user interaction.

Inbox supports:

• 1:1 conversations;
• group conversations;
• attachments;
• iMessage effects;
• reactions;
• threads.

Use the Embedded Inbox UI when you want to provide messaging inside your application without building and maintaining a custom conversation interface.

Configure Embedded Inbox

1. Open the LoopMessage Dashboard and select the required organization.
2. Go to Preferences → Embedded settings.
3. Add the origin of the page that will contain the Inbox to Allow domains.
4. Save the domain.
5. Copy the complete URL from the Embed code section.

The URL copied from the Dashboard contains the public token required to load the embedded UI. Keep the URL complete and unchanged.

Embed with HTML

<iframe
  src="YOUR_EMBED_URL"
  title="Inbox"
  width="100%"
  height="720"
  style="border: 0; border-radius: 12px;"
  loading="lazy"
  allow="clipboard-read; clipboard-write"
></iframe>

Replace YOUR_EMBED_URL with the URL copied from Preferences → Embedded settings. Do not construct the URL manually or remove its query parameters.

Embed in a React application

export function Inbox({ embedUrl }) {
  return (
    <iframe
      src={embedUrl}
      title="Inbox"
      style={{
        width: '100%',
        height: 720,
        border: 0,
        borderRadius: 12,
      }}
      allow="clipboard-read; clipboard-write"
    />
  );
}

Pass the complete URL copied from the Dashboard as embedUrl.

Access control and security

Embedded Inbox is intended for users who are authorized to view and use the relevant conversations. Do not publish the iframe as a public UI element or render it for every visitor to your website.

The embedded UI is protected by:

1. The public token in the embed URL.
2. The allowed domain configured in Preferences → Embedded settings.

The public token is visible to the browser and is not a replacement for your application’s authentication and authorization. Authenticate users in your application and render the iframe only when they are allowed to use Inbox.

If the public token is exposed, reset it in the LoopMessage Dashboard. The previous embed URL will stop working after the reset. Copy the new URL and update your application configuration wherever the old URL is used.

API availability

Inbox is a UI integration. You do not need to call the Conversation API to display the embedded UI or to send and receive messages from it.

Use the Conversation API separately when your backend needs programmatic access, automation, webhooks, or message processing outside the Inbox UI.