Live check
Machine-readable status (no API token):
GET https://cascade.kz/api/health
In the response:
checks.whatsapp.online/total— ready platform WA sessionschecks.telegram.online/total— ready TG sessionschecks.sms.configured— whether an SMS provider is connected (usuallyfalsefor now)ok: falseand HTTP 503 — if the DB is unavailable or there is no live messenger session
Lightweight Laravel probe: /up.
What counts as “service healthy”
- The HTTPS site and cabinet open on cascade.kz.
/api/healthreturnsok: trueand there is an online WhatsApp or Telegram session.- API requests with a valid Bearer token reach
POST /otp/sendandPOST /otp/verify. - Required channels are enabled in the cabinet (WhatsApp / Telegram; SMS — only after a provider is connected).
Local “it doesn’t work” causes, not a platform incident
| Symptom | Common cause |
|---|---|
401 |
Missing or wrong API key |
422 “Insufficient tokens” |
Need a top-up |
422 about the channel |
Channel disabled in the cabinet |
422 about SMS not connected |
Platform SMS provider is not configured yet |
| Code does not arrive | Wrong number, resend cooldown, recipient channel |
See API errors, statuses, FAQ.
Channels
WhatsApp and Telegram are the working platform channels (usually 1 token per successful send). SMS is reserved in the API and billing (16 tokens), but the external SMS provider is not connected yet: channel=sms ends with a “channel not connected” error. Marketing price orientation — from 1 ₸.
Updates
API and product changes are recorded in the changelog. For integration use the documentation and examples.