Message Management
Send Message
Send messages to specified channels
POST
Overview
Send messages to specified channels, supporting various message types including text, images, files, and more.Request Body
Required Parameters
Base64 encoded message content
Sender user ID
Target channel ID
Channel type (1=personal channel, 2=group channel)
Optional Parameters
Message header information
Client message number for deduplication and status tracking
Stream message number
Message expiration time (seconds), 0 means no expiration
Specified list of subscribers to receive the message (only valid for CMD messages)
Subscriber user ID
Response Fields
Server-generated message ID
Message sequence number
Client message number (echo)
Status Codes
| Status Code | Description |
|---|---|
| 200 | Message sent successfully |
| 400 | Request parameter error |
| 403 | No sending permission |
| 500 | Internal server error |
Message Type Examples
According to WuKongIM protocol specifications, here are recommended Payload structure examples:Regular Messages
Text Message
Text Message (with @ functionality)
mention.all: Whether to @everyone (0=@users, 1=@everyone)mention.uids: If all=1, this field is empty
Text Message (with reply)
Image Message
GIF Message
Voice Message
timeTrad: Voice duration (seconds)File Message
size: File size in bytesCommand Message
System Messages
System message type must be greater than 1000
Create Group Chat
Message settings:NoPersist:0, RedDot:0, SyncOnce:1
Add Group Members
Message settings:NoPersist:0, RedDot:0, SyncOnce:1
Remove Group Members
Message settings:NoPersist:0, RedDot:0, SyncOnce:1
Group Member Kicked
Message settings:NoPersist:0, RedDot:1, SyncOnce:0
Update Group Name
Message settings:NoPersist:0, RedDot:0, SyncOnce:1
Update Group Announcement
Message settings:NoPersist:0, RedDot:0, SyncOnce:1
Recall Message
Message settings:NoPersist:0, RedDot:0, SyncOnce:1
Command Messages
Basic Command Message
Message settings:SyncOnce:1
Group Member Info Update
Upon receiving this message, the client should incrementally sync group member informationRed Dot Clear
Upon receiving this command, the client should clear the red dot for the corresponding conversationUsage Examples
Best Practices
- Message Deduplication: Use unique client_msg_no to avoid duplicate sending
- Message Queue: Add failed messages to retry queue
- Content Encoding: Ensure payload is correctly Base64 encoded
- Permission Check: Check if user has sending permission before sending
- Message Types: Strictly follow protocol specifications for correct message type numbers
- System Messages: System message types must be greater than 1000 with correct message flags
- Command Messages: Command messages should set SyncOnce:1 flag

