testMode enabled and do not connect to real WhatsApp recipients.
Use Sandbox to verify number-management, project-scoped session controls, and
signed-in desktop workflows before you register a production number. New
testing numbers are connected and available immediately. They remain simulated
and cannot contact real WhatsApp recipients. Their API-controlled device stays
linked across service and app restarts until you remove the testing number.
The public session APIs provide simulated equivalents for messages and media,
message mutations and acknowledgements, contacts, groups, channels, presence,
privacy, profiles, labels, business catalogs, and session lifecycle actions.
State changes are shared between the API-controlled device and Inspector, so
you can exercise the same multi-device behavior without contacting WhatsApp or
a real recipient.
Direct messages stay inside the project: the recipient must be another active
testing number in that project. Group and channel activity is routed among the
testing numbers that belong to the simulated conversation. Unknown, stopped,
removed, and cross-project direct recipients return 404 Not Found without
creating recipient state.
Available workflows
The QuickLink request identifies the project and includes
configuration.testing.
Choose a country, simulated profile, account type, reply behavior, and supported
failure scenario. Delegate an explicit subset to the recipient with editable.
A fixed country determines the generated phone number; profile fields do not
change the reserved identity. See QuickLink.
List the project sessions and select rows with testMode: true instead of
assuming a fixed number count or phone format.
Limits and billing
Sandbox testing numbers use the Free number tier:- 0 credits per online session-day.
- 5 messages per second per testing number.
- 1 GB of included data per testing number.
- 5 inbound and 5 outbound calls per month, with no overage.
- 1,000 serverless calls per month.
- No real-number registration or campaigns.
Inspector devices
In Inspector, choose Open beside a testing number. Your Polymorfa account owns that session through Inspector, and the app connects as a native linked device. Closing or signing out retains the device for reconnection. Inspector ownership does not broaden your team, project, or session-control permissions.Where to go next
Sandbox quickstart
Create, list, and remove a testing number.
Number pool
Manage testing numbers through the public Platform API.
Sandbox limits
Review the current Free number-tier limits.
Phone controls
See linked devices, send as the phone, and unlink a device.
Inspector ownership and devices
Open a testing session from a signed-in desktop device.