Sandboxes are isolated test environments on the public API. There is no separate sandbox hostname: normal /v1/... requests go to https://api.withflintpay.com, and the sandbox-bound flint_test_... key you authenticate with decides which sandbox handles the request. Every developer merchant gets one default sandbox automatically; create additional sandboxes for CI, partner QA, or pre-release testing.
Test keys are permanently bound to one sandbox at creation, so there is no per-request sandbox header to manage. Resetting a sandbox clears its data in place while keeping the same sandbox ID and key bindings, which is the fastest way to return a disposable QA environment to a clean state. The default sandbox cannot be archived or reset.
See the Testing guide for the runtime testing loop, including test cards and simulating payment outcomes.
