How are people handling WhatsApp OTP when the official API isn't available in their country?

reddit SaaS · 原文链接 ↗ · 53 分

I'm building a small app for Syria where the official WhatsApp Cloud API currently isn't available for sending to Syrian numbers. Since phone number is the only login method, OTP delivery is a core requirement. I've tested self hosting WAHA (Baileys) with a dedicated WhatsApp number. Technically the setup works and messages arrive within seconds, but the account isn't reliable enough for production. A fresh number was restricted after roughly ten test messages. The session then failed, I had to relink it manually, and WhatsApp later revoked the linked device. I also triggered another re

五维评分

AI 分析

痛点：在WhatsApp官方API不可用的国家（如叙利亚），需要手机号OTP登录的应用无法可靠、合规地通过WhatsApp送达验证码，自建非官方方案易被限制。

目标用户：在WhatsApp官方API未覆盖国家运营、且以手机号+OTP为核心登录方式的小型应用开发者/团队。

证据：Since phone number is the only login method, OTP delivery is a core requirement. ... A fresh number was restricted after roughly ten test messages. ... A competitor in the same market is clearly doing this successfully, so there must be a practical architecture I'm missing. And yes whatsapp is preferred over SMS

变现：按量付费的OTP多通道API（官方BSP+短信+语音+Telegram降级），或面向受限地区的合规送达标代理/架构咨询服务。

MVP：两周内做一个统一OTP API：优先走可用地区的官方WhatsApp BSP，受限国家自动降级到本地短信/语音/Telegram；提供发送状态、重试和成本看板。不要承诺纯非官方WhatsApp稳定送达。

竞品：Twilio、Infobip、MessageBird、360dialog、WAHA、Baileys、本地短信聚合商

摘要：发帖人为叙利亚应用开发者，手机号是唯一登录方式，官方WhatsApp Cloud API无法向叙利亚号码发送OTP。他自建WAHA/Baileys测试约10条消息后账号被限制、设备被撤销，想知道生产环境如何可靠送达OTP，并称同市场竞品已成功且WhatsApp优于SMS。