Choose what to test
The sandbox stays running, on the same build trdrs releases to production. While a release restarts it, a
request that waits more than 30 seconds for the engine to start is refused with
503
engine_starting and does nothing, so send it again. Accounts and keys survive a restart, and
background work picks up again when the engine starts.
Sandbox Trading API keys and pre-registration keys start trdrs_sk_sandbox_ and expire after 30
days. Venue keys start trdrs_vk_sandbox_ and a Connect app’s API keys start trdrs_ck_sandbox_,
and both last as long as the owner who created one chose. A sandbox key works only in
the sandbox.
Set your venue’s brand
Set your venue’s name, description and logo before you run conformance, so your traders see your brand on their accounts. Use the back office or the Venue API. The name is at most 60 characters and the description at most 140. A logo is a square PNG from 256 to 1,024 pixels on a side and at most 512 KiB. Your brand applies to the venue’s existing accounts and every account you issue next. The account number stays visible, and an issued account’sprovider value in the API stays paper. A
trader’s own Demo keeps its own identity. Branding changes how an account looks, never how it
trades or who owns it.
You don’t need a payment, a passing conformance run or a production listing to preview your brand in
the sandbox.
Issue test accounts
Issue sandbox accounts through your venue withPOST /api/venues/{venueId}/accounts. The account
needs a group with a route and a published risk policy. The evaluation quickstart
sets up both, and Venue accounts covers the whole account lifecycle.
Every account is issued in USD. Choose the policy by what the account trades:
An account’s money is posted in cents. The account trades the instruments your venue activates in
every product class its policy offers, all from its one balance.
Use sandbox accounts you can afford to change. The sandbox is separate from production, but an
order, a reset or a stage test still changes the balances and history of the accounts it touches.
Keep payments in your own systems
The sandbox exists to build and test integrations. Your checkout, subscriptions and payment provider stay in your own systems. You don’t need any payment setup to get a key, issue test accounts or run conformance.Move to production
Production is its own environment, with its own keys and base URL. Set both explicitly in your configuration, and never infer the environment from a failed request, because a key from one environment can’t authenticate in the other.- Venue keys. A verified owner creates them on the back office’s API keys page, under
Production. They start
trdrs_vk_production_. A production venue’s keys are made in a back office installed withTRDRS_ENVIRONMENT=productionand connected to it. The venue routes are served in the sandbox, and production access is arranged when your venue qualifies. - Trading API and pre-registration keys. Production keys come with your commercial agreement. Profile API access lists and revokes Trading API keys, and the back office’s API keys page lists and revokes pre-registration keys.
- Connect apps. A passed Connect conformance run earns a Connect
pass, and the pass opens your app’s production once its billing is set up, with the current terms
accepted and a card on file. Its production API keys start
trdrs_ck_production_, and its production websites are exacthttpsorigins that apply at once. - Your data. Nothing is copied from the sandbox. Accounts, balances and provider credentials start fresh in production.