Skip to content

Updates

Changelog

Key milestones of the Cascade OTP product on cascade.kz.

Quick Answer

Cascade evolves as an outbound OTP delivery API; current endpoints are /otp/send, /otp/verify, /links/*, /group/send.

Summary

Public log of significant changes to the OTP and short-link delivery platform.

Key Takeaways

  • Core API contract is stable: Bearer + JSON.
  • Channels: whatsapp, telegram, sms.
  • Follow the documentation and OpenAPI.

Related Questions

2026-07 — Public content documentation

  • Expanded public pages: FAQ, use-cases, compare, services.
  • Product boundaries fixed: Cascade = outbound OTP delivery, not virtual number rental.

Earlier — API core

  • POST /api/otp/send — send OTP (optionally with a short link in the same message).
  • POST /api/otp/verify — verify the code.
  • POST /api/links/shorten — shorten a URL without charging for delivery.
  • POST /api/links/send — shorten and send a link to the phone.
  • POST /api/group/send — message to a WhatsApp group.
  • Bearer auth from the company cabinet.
  • Billing per docs: WhatsApp/Telegram = 1 token, SMS = 16 tokens.

How to use the changelog

For integration always cross-check the documentation, OpenAPI and API sections. Questions — in FAQ. Prices — on /pricing.