Your uptime monitor checks if your API returns 200. It doesn't check if your OTP actually arrives.

Описание и применение

OTP‑watch позволяет проверять доставку одноразовых паролей по SMS и email в реальном времени, заполняя пробел, оставляемый синтетическими мониторингами, которые только проверяют ответы 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

Источник