Skip to content

For testing

Regression and controlled OTP API checks: limits, errors, pricing.

Quick Answer

Regression and controlled OTP API checks: limits, errors, pricing.

Summary

Regression and controlled OTP API checks: limits, errors, pricing. 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

Automated tests and regression around send/verify, not “buy a number and wait for messenger channels”.

What to cover

  • 200 on send/verify happy-path
  • 401 without/with a broken key
  • 422 on a bad phone
  • 429 when limits are exceeded
  • Cost difference WA/TG vs messenger channels on /pricing

For manual stands see /use-cases/qa. DX: /use-cases/developers.

Test Cascade with your own flow

Open the dashboard and test delivery on your own flow.