Sandbox
1. Use a sandbox key
Sandbox keys (dk_test_…) see the same markets, rules and prices, but their projects are matched only to Ducto's scripted installer, money is simulated and nothing is emailed or texted. Live and sandbox data never mix.
2. Accept as the scripted homeowner
A sandbox booking is accepted by the scripted homeowner, not a real person.
3. Time travel
The scripted installer confirms, checks the site, pulls permits, records serials and submits each payment stage, and the homeowner approves, as far as you ask (confirmed, in_progress or completed). It stops where the job waits on you, such as shipping and delivery, and says so in waitingOn.
The reference store
Acme Home Supply (examples/acme-store in Ducto's repository) is a store built on the SDK alone in retailer-merchant mode: catalog mapping, the install widget, checkout and booking, shipping when Ducto releases the order, and every webhook. It runs end to end in the sandbox on every change to Ducto, and it's the place to start a real integration. See the retailer guide.