Skip to main content
There is one host. The environment lives in the key, not the URL, so switching environments is swapping a credential, never rewriting endpoints.

​
What happens in sandbox

Sandbox is not a stub. Every endpoint returns the production response shape with realistic values, so you can build and demo your entire front end against it. The one absolute: no real financial activity ever occurs on a sandbox key.
  • Same contract, both environments. Sandbox returns production response shapes end to end, so a green sandbox integration ports to production by swapping the key.
  • Unmistakable in logs. The scripx_test_ prefix is deliberate: nobody reading a log, dashboard or statement confuses a rehearsal with a live trade, and sandbox artefacts must never be represented as real trades.
  • Isolation is by party. A sandbox key is bound to a test firm; it cannot see or touch anything belonging to a live firm.

​
Build your UI against sandbox

Everything you need to build client-facing screens works on a sandbox key alone:
  1. Market snapshot and the SSE stream for a live price panel.
  2. Quote → order → positions for the full trade flow.
  3. Webhooks for real-time status in your UI, signature verification included.
  4. The OpenAPI spec and SDKs to generate typed clients.
Keys are issued per environment and are never interchangeable: a sandbox key on production data fails auth, it does not degrade quietly. Write to amin@eximfiles.io when you are ready for a production key.