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

Service

OTP and user verification: Steam

This page is about outbound OTP delivery in your product, not about buying numbers to register on Steam.

Quick Answer

Use Cascade when YOUR service sends a code to the user. Cascade is not intended for renting numbers for Steam.

Summary

Cascade helps send a code to the user's phone. This is not a disposable number for bypassing registration on Steam.

Key Takeaways

  • Outbound OTP ≠ virtual number rental
  • API send/verify
  • See /faq and /compare

Related Questions

Contents

  1. Read this first
  2. How to get OTP for a user of your product
  3. Common mistakes
  4. Next
  5. How this relates to Cascade
  6. Practical steps
  7. Limits and honest expectations

Read this first

Cascade is not a service for buying virtual numbers to register accounts on Steam. If you need a disposable phone number from a third-party marketplace — that is a different product class (see comparisons).

How to get OTP for a user of your product

  1. The user provides their number.
  2. Your backend calls Cascade POST /otp/send.
  3. The user receives a Verification Code in WhatsApp/Telegram/SMS.
  4. You verify the code via POST /otp/verify.

Common mistakes

  • Confusing outbound OTP with number rental
  • Putting the API key in the client
  • Ignoring rate limits
  • Not handling 422/429

Next

API · FAQ · Use cases · Pricing · Blog

How this relates to Cascade

Cascade is an outbound delivery service for OTP and short links to the user's real phone via WhatsApp, Telegram or SMS. It is not a disposable phone numbers marketplace and not virtual-number rental for signing up on third-party sites. API base URL: https://cascade.kz/api. Authorization — Authorization: Bearer <token> from the company cabinet. Price orientation — from 1 ₸; token billing: WhatsApp/Telegram = 1 token, SMS = 16 tokens (see the documentation).

Practical steps

  1. Register a company and get an API key.
  2. Call POST /otp/send with the user's number.
  3. The user enters the code in your form.
  4. Confirm the code via POST /otp/verify.
  5. On errors see the error reference and FAQ.

Setup usually takes about three minutes. Also useful: SDK, use cases, comparisons and blog.

Limits and honest expectations

Do not promise “100% delivery always”: messengers and SMS depend on the network, user settings, and channel availability. Use cascade logic where it fits, monitor history in the cabinet, and do not store the API key on the client. If SMS did not arrive, check the channel, token balance, phone format, and resend with a reasonable interval. For product solutions it is better to start with WhatsApp/Telegram and keep SMS as a more expensive fallback.

FAQ

Can I get a number through Cascade to register on Steam?
No. Cascade does not issue virtual numbers for third-party platforms. It sends OTP to your user's number.
How do I verify a user in my service if they came from the Steam ecosystem?
Collect the phone, send OTP via the Cascade API, verify the code, and continue onboarding.
Which channel should I choose?
WhatsApp or Telegram is often cheaper and more convenient; SMS is a fallback.
Documentation API Pricing FAQ