Skip to content

Use case

For QA

Checking registration and login flows on stands with real delivery channels.

Quick Answer

Checking registration and login flows on stands with real delivery channels.

Summary

Checking registration and login flows on stands with real delivery channels. Outbound OTP to a real user number via the Cascade API.

Key Takeaways

  • Outbound OTP, not number rental.
  • Key only on the server.
  • Links: /docs /api /pricing.

Task

QA checks that OTP arrives and verify succeeds on staging/preprod — without renting virtual numbers.

How to run scenarios

  1. A separate API key for the stand.
  2. Team test numbers (real QA phones).
  3. POST /otp/send → enter code → POST /otp/verify.
  4. Negative cases: wrong code, TTL, 429.

Link to load testing: /use-cases/testing. Errors: /api/errors.

FAQ

Is Cascade suitable for QA?
Yes, if you send a code to your user on their number.
Where to start?
Key → /otp/send → /otp/verify → monitor in the cabinet.