Sandbox flow
The website provides a reviewable Sandbox route and links from Trial and Developers. It does not issue keys or send messages.
Sandbox
Sandbox
A target test environment for SMS integrations before production. The public website currently describes the surface; backend Sandbox behavior is not published as current production behavior.Environment separation
Sandbox and production should stay separated by credentials, balance, logs, contacts, sending rights and readiness gates.
Virtual billing
Virtual balance, charge records and statements are target behavior and require backend confirmation before public contract publication.
Delivery simulation
Delivery statuses and rejects should be simulated without real SMS or carrier traffic when the Sandbox backend exists.
Virtual inbox
Inbox previews are planned for test messages only. Supported preview modes and retention period remain open decisions.
Webhook tests
Test webhook sending is planned and must not be presented as current production behavior until endpoints are confirmed.
Current status and open decisions
- No real SMS, carrier traffic, production balance, production API keys or live delivery reports are claimed by the current website.
- Sandbox volume limits remain an open product decision.
- The difference between simulated send and verified-number live trial test remains explicit.
- Trial account tariffs, billing shape, virtual inbox previews, contact isolation and log retention require backend confirmation.
- Plugin and no-code Sandbox modes are not published as current behavior.