I have a WhatsApp Cloud API setup that can send messages flawlessly through PHP cURL, yet the accompanying Webhook remains silent. The URL verifies just fine (Facebook’s GET handshake succeeds), but no POST events ever reach it—no sent/delivered/read receipts, no incoming messages, no template-status notifications. 1. Display name has been approved. 2. Message templates were also created and approved. And template messages can be sent through php cUrl api. And the end user mobile is correctly receiving the template messages. Key facts you should know before diving in: • I believe the problem lies in the configuration settings inside the Facebook Developer Dashboard rather than my server code. • The callback URL and verification token have been double-checked and match the values in the Dashboard. • The same server endpoint already receives POST events from a different WABA, so the listener script and hosting environment are proven. Your task is to trace and eliminate whatever is blocking or mis-routing callbacks for this specific phone number / Business account. I’m looking for a clear diagnosis plus a concrete fix applied directly to the Meta settings or, if it turns out I’ve missed something hidden on the server side, the appropriate code tweak. Acceptance is simple: after your work, I must see live POST payloads for message status updates, inbound texts, and template-status events arriving at the endpoint, visible in my server logs or echoed JSON. Once confirmed, please document what was changed so I can replicate it in the future. IMP: You should work on AnyDesk. & do not bid without proper experience on WABA settings.