Your uptime monitor checks if your API returns 200. It doesn't check if your OTP actually arrives.
说明与用途
OTP‑watch 能实时验证短信或邮件 OTP 的投递情况,弥补仅检测 API 响应的合成监控工具的不足。
问题
Synthetic monitoring tools only verify API responses, not whether OTPs sent via SMS or email actually reach the intended recipient or how long delivery takes, leading to undetected delivery failures.
结果
OTP-watch fills a critical gap by confirming OTP delivery and latency, reducing support tickets and improving user onboarding reliability.
工作流
- 1. Request a unique key via POST /keys with target email or phone.
- 2. Initiate a check with POST /checks specifying channel (sms/email) and timeout.
- 3. Trigger the OTP send to the provided target using your application.
- 4. Poll GET /checks/:id to retrieve status and latency.
- 5. Integrate polling into CI or cron to fail on timeout or missing delivery.
证据
Every synthetic-monitoring tool (Checkly, Pingdom, Better Stack, Datadog Synthetics) can tell you your signup endpoint responded correctly. None of them tell you whether the SMS or email your OTP provider promised to send actually showed up in a real inbox or a real phone
I built otp-watch — a small hosted service that answers exactly that question, live at https://otpwatch.flo-voice1.com
- 记录日期: 2026-09-07T04:36:36.124Z