Skip to content

Test mode

Build against a simulated carrier.

Test mode is on every workspace, including the free trial. A dak_test_ key, or the test toggle in Settings, runs consent checks, quiet hours, internal do-not-call, opt-outs, dedupe, daily caps, approval tokens, webhooks, and analytics. Nothing is dialed. Credits are not held and are not spent.

Create a test key
curl -X POST $DROPAGENT_BASE/api/v1/api-keys \
  -H "Authorization: Bearer $DROPAGENT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"name":"Local agent","mode":"test"}'

Turn the whole workspace to test mode with {"testMode": true} on PATCH /api/v1/settings. Live da_live_ keys keep working for reads. While the toggle is on they also use the simulated carrier.

Magic test numbers
NumberResult
+15555550100Delivered
+15555550101Failed (simulated_failure)
+15555550102Blocked, landline
+15555550103Opted out
+15555550104Delivered, then an inbound reply: “Yes, please call me back.”

These numbers only change the simulated result. A contact without a consent record is still blocked before the carrier step. Outside quiet hours, the drop waits. Bulk sends still need a dry run and a confirm token. MCP exposes the same notes through describe_test_mode.