Skip to content

API

Webhooks

The core Cascade contract is a synchronous JSON send/verify response.

Quick Answer

The basic OTP flow does not require a webhook: check success in the API response.

Summary

For integration it is enough to handle the HTTP response and the success field. Confirm separate webhook events in the current documentation.

Key Takeaways

  • Send/verify are synchronous.
  • Unknown details — under “Needs verification”.
  • See OpenAPI and documentation.

Current integration model

Typical Cascade scenario:

  1. Backend calls POST /otp/send.
  2. User enters the code.
  3. Backend calls POST /otp/verify.
  4. The decision is made from success in JSON.

This is enough for login, registration and operation confirmation.

Webhooks

Needs verification

The public specification of separate outbound webhook events (delivery callbacks, etc.) may expand. Before production integration, cross-check:

Until webhooks are confirmed in your setup — rely on synchronous responses and history / statuses in the cabinet.

See also FAQ, errors.