Content moderation overview
The Nexconn messaging service provides content moderation features to help ensure safe and compliant messaging in your application.
- Profanity filter: A basic built-in text filtering mechanism (default limit: 50 words). This is a baseline protection and does not replace a professional content moderation service.
- Pre-messaging webhooks: Route messages to your own server for custom moderation or integration with third-party moderation services.
Profanity filter
The client SDK does not provide management APIs for the profanity filter. It only provides a callback when a message is blocked. See Moderation interception callback.
The profanity filter scans text message content for matching words and either blocks the message (prevents delivery) or replaces the matched words before delivery.
Supported languages: Chinese, English, Japanese, German, Russian, Korean, Arabic.
Management options
| Action | Client API | Server API |
|---|---|---|
| Add profanity words | Not available | Batch add words |
| Remove profanity words | Not available | Remove words |
| Remove multiple words | Not available | Batch remove |
| List profanity words | Not available | List words |
Default behavior
- Maximum of 50 profanity words by default.
- Only applies to messages sent from client SDKs (not Server API messages by default).
- Only scans the built-in text message type (
NC:TxtMsg). Supported in direct, group, open, and community channels.
Configuration
- Enable Moderate messages sent by server API on the Console to apply filtering to messages sent via the Server API.
Pre-messaging webhooks
For custom moderation or third-party integration, subscribe to the *:pre_messaging webhook events in the Console under Chat > Webhooks. Your server can then approve, reject, or modify message content.
See the pre-messaging webhooks documentation for details.