Ignore one contact on an application channel
POST/v1/communication/channel/:applicationChannelId/ignored-contacts
The identifier is ignored only inside the Hub; it is not blocked at WhatsApp, Instagram, Messenger, SMS, Telegram or Web Chatt. Matching inbound events, provider echoes and contact-specific message statuses are discarded before new messages, sessions, billing or customer webhooks are created. WhatsApp COEX history threads for ignored contacts are also skipped. Account-wide events without a contact identity continue normally; existing conversations and charges are not removed, and sending through the Hub API is not blocked. WhatsApp accepts phone or BSUID; Instagram and Telegram accept ID or username; Messenger accepts ID; SMS accepts phone; Web Chatt accepts visitor_id. Phone values are compared as digits, usernames case-insensitively without the leading @, and IDs and BSUIDs exactly. Prefer provider IDs: usernames match only when the provider supplies them. Web Chatt visitor IDs are controlled by the browser and can change when local data is cleared. An already-connected ignored Web Chatt visitor receives message.ack with status ignored; an ignored visitor connecting again is closed with WebSocket policy code 1008.
Request
Responses
- 201
- 400
- 401
- 404
- 409
Contact ignored on this channel.
Invalid identifier or type unavailable for this channel.
Missing or invalid authentication.
Channel unavailable to this principal.
The normalized identifier already exists on this channel.