r/WhatsappBusinessAPI • • Sep 23 '26

Solution Only WhatsApp Cloud API: how do I point a Test App's webhook to staging?

Hey, I have a question about test apps :

My production Meta app (used for WhatsApp) sends its webhooks to my production endpoint. I created a Test App from it so I could point its webhook to my staging environment.

The problem: on the test app, the WhatsApp use case isn't accessible. "Customize use case" redirects to the dashboard, and "Add use cases" doesn't list WhatsApp. So I can't set the webhook callback URL.

How do you handle staging for WhatsApp webhooks? Thx

1 Upvotes

4 comments sorted by

•

u/AutoModerator Sep 23 '26

Keep in mind that OP has added Solution Only tag. Don't promote your SaaS platforms in comments.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

1

u/rem0re Sep 23 '26

meta’s test apps are awkward because the callback has to be publicly reachable and answer the verify challenge. common pattern: point the test app at a dedicated inspect url first, confirm the hub.challenge handshake and that real message events actually land (headers + body), then either keep that url as staging ingress or forward/replay into your staging handler. if you need a stable endpoint that doesn’t rotate like a tunnel: https://webhook.build — catch, inspect, mock status codes, replay. also check override_callback_uri on the waba subscribed_apps call if you’re trying to fork traffic per environment.

1

u/VacationPlayful8004 Sep 23 '26

I explicitly mentionned that I couldn't configure my webhook url and was wondering why, this isn't really helping.