⌘K

Get StartedGuide

Sandbox

Purpose, isolation, credentials and safe testing boundaries of the Sandbox environment.

On this page

Purpose

Sandbox is an isolated environment for evaluating Solia and rehearsing a complete integration with synthetic data. It uses the same Partner API paths, scopes, error envelope and event contract as Production.

Important

Sandbox exploration does not satisfy Production readiness prerequisites. Production readiness is re-derived from Production evidence only.

Data and what persists

  • All data is synthetic evaluation data. Do not enter real patient information.
  • Configuration, Programs, orders, results, webhook subscriptions and delivery history you create persist inside that Sandbox workspace until it is reset.
  • Reset returns a Sandbox to its blank baseline; it never touches another workspace or Production.
  • Nothing in Sandbox contributes to Production metrics, attention items, connection health or authorization decisions.

Credentials and isolation

  • Sandbox keys use the sk_sandbox namespace; Production keys use sk_live. A key cannot read the other environment.
  • Sandbox-issued keys are never granted webhooks:manage; webhooks are managed by a laboratory administrator.
  • Laboratory connection adapters, endpoints and credentials are configured separately per environment and are never copied from Sandbox to Production.

Onboarding and exploration

  • A new self-service workspace starts as a blank, isolated Sandbox; nothing is cloned from another laboratory.
  • Authorized members can explore Overview, Orders, Customers, Results, Integrations and Production readiness before their setup step is current. Viewing a surface never advances setup.
  • After activation the Sandbox remains as a paired companion to the Production workspace, available for further synthetic rehearsal without reopening onboarding.

Deterministic testing

GET/v1/sandbox/order-fixturesList synthetic order-request fixtures
GET/v1/sandbox/scenariosList deterministic sandbox scenarios
POST/v1/sandbox/orders/{orderId}/simulateAdvance a synthetic order through a scenario

Scenarios: happy_path, partial_then_final, specimen_rejection_recollection, critical_result, transmission_failure_then_retry, corrected_result, webhook_failure_then_replay, specimen_rejected. Each scenario is a fixed ordered set of canonical state changes, so the same scenario produces the same event types every time.

Fixtures illustrate request shapes only; they never bypass a Program's real requirements.

Safe testing boundaries

  • Simulation is refused outside Sandbox and never affects a Production order.
  • Sandbox webhook deliveries go only to endpoints registered for Sandbox.
  • Sandbox has no live payment, clinical release or Production laboratory side effects.

Related resources