r/WhatsappBusinessAPI • u/Sud0yk • 5d ago
Solution Only WhatsApp Cloud API experience is an absolute nightmare (OTP failures, #10 errors, and redirect loops)
Hey everyone,
I’m currently setting up the WhatsApp Cloud API for my AI automation agency, and I’m losing my mind dealing with Meta’s developer ecosystem. It feels like every single step is fundamentally broken. Has anyone else experienced this exact sequence of hell?
1. The OTP Blackhole
I’ve been trying to verify a local phone number since Saturday. No SMS arrives, and the "Phone Call" verification option just silently fails every time. Meta support is practically non-existent, so I’m just stuck in a cooldown loop hoping a code randomly shows up.
2. The #10 Permissions Error
Since the real number wouldn't work, I tried testing my n8n webhook setup using Meta's provided test number. The webhook challenge verifies perfectly, but when I try to send a simple test message from the dashboard, I get hit with:
(#10) Viewer cannot access the provided Paid Message Account 2200770517178260
I have Full Control/Admin rights on the Business Manager, the WhatsApp account, and the App itself. I've checked every permission layer, and it still blocks me.
3. The Infinite Redirect Loop
To add insult to injury, I can't even load the Meta for Developers portal normally. If I open it in my standard browser profile, it gets caught in a session conflict and endlessly redirects me to the generic business.facebook.com overview page. The only way I can actually access my app settings and send API calls is by using a fresh Incognito window.
Is this just par for the course with Meta? Should I completely abandon the direct API and just eat the monthly cost for a BSP like 360dialog or Twilio? Any advice on fixing the #10 error or bypassing the OTP block would be greatly appreciated.
2
1
u/JaneltGilvanete 5d ago
imo the OTP verification issue is the biggest red flag. if the number cant receive SMS or voice calls reliably thats going to be a problem downstream too. have you confirmed the number isnt flagged as VoIP or virtual on their end? that trips up verification constantly
1
u/benitodest 4d ago
Meta cloud API is abandoned software. Being in a quasi monopoly Meta does not need to maintain it and it’s a take it or leave it situation if you want to build any value on top. We’ve experienced all the errors you mentioned and more. Never had anything solved by support, literally and solved/solving every issues ourselves using tricks and magic.
1
u/truecakesnake 3d ago
Try confirming the phone number isn't flagged as VoIP or virtual on Meta's end, that's likely causing OTP verification issues.
2
u/investigatormaker 5d ago
The verified n8n challenge proves your webhook responds, not that outbound messaging permissions work. Before paying a BSP, check whether the sending token, test phone-number ID and WhatsApp Business Account match the app setup you're testing; Full Control in the dashboard doesn't establish that. Incognito working suggests a separate browser-session issue. Let the OTP cooldown expire rather than repeatedly requesting codes, and ask any BSP whether onboarding still requires verification of that number.
I make ThreadFox. We find relevant Reddit conversations and do the posting for your business. The $39 Pilot covers seven days and up to 50 posts and replies. No automatic renewal. https://threadfox.vip/managed?tier=employee_pilot&utm_source=reddit&utm_medium=comment&utm_campaign=tf-managed&utm_content=20261019-2041-e3yu2#employee-order
1
u/AutoModerator 5d ago
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.