Block Users API guide | Developer Documentation

WhatsApp contact blocking: ChatArchitect availability

ChatArchitect does not support blocking or unblocking a contact in WhatsApp through its API or ready-made integrations. This availability was confirmed on 8 October 2026. The imported Meta Block Users API describes a separate implementation; it is not an action available through your ChatArchitect connection.

Keep these actions separate

Use the permission and audience guide when a person asks you to stop marketing. Record the request and update each responsible sending workflow. Excluding the contact from one list is not proof that every scheduled job or other application has stopped.

If unwanted messages or replies continue

• Identify the connected business number and the CRM/help desk or application receiving the conversation.
• If your own workflow keeps sending, identify its responsible rule, audience or job and use that tool's supported controls to change it.
• If the issue is the display or handling of incoming messages, check what local filtering or conversation controls the receiving tool actually provides.
• Keep the desired WhatsApp-level restriction separate from these local actions when asking support about the case.

This guide does not establish a universal CRM filter, an automatic stop across all integrations, or a block/unblock endpoint for the ChatArchitect service API. Do not send Meta Block API requests to that API or substitute customer App key and Secret into Meta Bearer-token examples.

Prepare the support request

Describe the tool, connected number, contact context and the unwanted behaviour. State which local action was taken and whether messages still arrive or your workflow still sends. Include relevant times with time zone and sanitized records if available; keep secret credentials out of the report. Support can clarify the available workflow, but blocking and unblocking in WhatsApp are not currently offered through ChatArchitect.