Skip to content
Cascade Cascade
Қазақша Русский English

Use case

For testing

Regression and controlled OTP API checks: limits, errors, token billing.

Quick Answer

Regression and controlled OTP API checks: limits, errors, token billing.

Summary

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

Related Questions

Contents

  1. Task
  2. What to cover

Task

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

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 SMS on /pricing

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

FAQ

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