Messaging API

The Unified Messaging API enables developers and product managers to access communication data from multiple messaging platforms through a single, standardized interface. Retrieve channels, messages, and events from Slack, Microsoft Teams, Discord, and other major messaging platforms - all with one API.

What is the Unified Messaging API?

Messaging platforms like Slack, Microsoft Teams, and Discord each have unique APIs with different authentication methods and data models. The Unified Messaging API normalizes these differences, allowing you to build once and support all major messaging platforms without maintaining separate integrations.

Messaging Data Objects

The Messaging API provides access to the following standardized objects:

• Channels: Channels, rooms, groups, and conversations
• Events: Message events, reactions, and activity notifications
• Messages: Chat messages, threads, and direct messages

Common Use Cases

Chatbots & Virtual Assistants

Build chatbots that work across Slack, Teams, Discord, and other messaging platforms. Create a single bot that can respond to messages, answer questions, and automate workflows across all platforms.

Message Analytics & Insights

Analyze communication patterns across messaging platforms. Track message volume, response times, channel activity, and team collaboration metrics from Slack, Teams, or any supported platform.

Cross-Platform Messaging

Create tools that sync messages between different messaging platforms. Bridge communications from Slack to Teams, or enable cross-platform team collaboration.

Compliance & Archiving

Build compliance and archiving tools that capture messages from multiple messaging platforms. Store, search, and analyze messages for regulatory compliance and e-discovery.

Workflow Automation

Automate workflows triggered by messaging events. Create tools that perform actions based on specific messages, keywords, or reactions across all messaging platforms.

Handling threaded messages

Use the parent_id for maximum flexibility in handling threaded messages.

Note: parent_message_id and root_message_id are deprecated.

parent_id: Represents the immediate predecessor message in a thread.
This allows you to identify which message a given message directly replies to.

Threading relationships form a tree of messages, where each reply points to its parent

Replying to Messages

• Set parent_id to the ID of the message being replied to.

This ensures the reply is properly threaded and appears under the correct message across all integrations that support threaded conversations.

Listing Messages in a Thread

You can retrieve messages within a thread using the parent_id relationship.

Using the expand Filter

When listing messages, you can set the expand filter to true to automatically include all nested descendants of a message, not just its immediate children.
This provides a full flat view of the thread hierarchy in a single query.

Consistency Across Integrations

Using the parent_id structure ensures:

• Consistent message hierarchy across sender and receiver systems.
• Simplified logic for reconstructing conversation trees.

If a message does not include a parent_id, it is treated as either:

• A standalone message, or
• The root of a new thread.

Working with Hierarchical Data in Messaging APIs

Messaging integrations typically organize data in a hierarchical (tree-like) structure. For detailed guidance on traversing hierarchical data, refer to our guide: How to traverse hierarchical data