For APIs that integrators build against
Sandbox GateCheck your API test mode, so an integration is fully validated before it touches real money, messages or data.
List your error codes and every documented outcome with the test value that triggers it. Your browser measures failure-path coverage against the 100% gate, holds every magic value to your real error codes, catches one value meaning two things, verifies the Luhn digit of every test card, checks that every event fires on demand and no flow needs real waiting, then checks keys, isolation, reset, quotas and the path to live. Then the test-mode design, and the cutover.
The platform, and a short interview free
Error codes, outcomes and their triggers free
Events, time and data free
Isolation, keys, quotas and abuse free
The path to live free
The checks free
What the page flags
Every outcome and its trigger
Events and time
Area by area
Your test-value catalog free
The page integrators read: every outcome per operation, its trigger and its real code - with the gaps marked.
Catalog (Markdown)
The test-mode design metered
Pricing as soon as the session is ready...
Sign inThe reply could not be read. Here it is as it came back:
Caveats
Caveats
The page's check of this reply
Saved sandboxes
How it works - and what is sourced
The checks follow the skill: a stateful sandbox, never a mock; every documented outcome triggerable by a magic value or a simulation endpoint (a gate at 100%), each mapped onto a real code from your published catalog and labelled per operation when one value means different things; every async event fireable on demand and every time-dependent flow testable by a clock or aging fixtures, never by waiting; synthetic seed data, reset endpoints and periodic cleanup; a type prefix plus _test_ or _live_ and a named wrong-environment error; production limits or an aggregate cap for the sandbox; card-testing controls on live checkout; an explicit environment-not-approved error, a four-step cutover checklist with a live canary, and the five cutover pitfalls published. The Luhn check is the standard mod-10 check digit every card form validates.
The rankings follow the skill: the soft toggle by default, the hard separate copy for parallel teams, compliance-demanded isolation, per-tenant infrastructure or a greenfield platform - never within a budget of weeks; magic values by default, simulation endpoints when outcomes stop being a function of input, a fixture builder for data aggregation.