Skip to content

Cabinet

History

Send history is available in the company cabinet.

Quick Answer

The main history source is the Cascade cabinet; confirm API methods in the documentation.

Summary

For audit and support use the cabinet: who, where, which channel. Confirm the history API contract in OpenAPI.

Key Takeaways

  • The cabinet is the main UI for audit.
  • Do not store OTP in your logs.
  • See statuses and errors.

Where to look

In the cabinet you get operational data on your company's sends: useful for user support (“code did not arrive”).

Needs verification

The exact public REST endpoint for full history export may differ by API version. Cross-check OpenAPI and the documentation.

What to log on your side

Allowed: phone (masked), purpose, success, message, time, your user id.
Forbidden/undesirable: raw API token, full OTP code.

See statuses, FAQ, use-cases.