Start in the explicit sandbox environment. Confirm the account response, instrument constraints, and a unique idempotency key before a write.
Select a numbered step to zoom straight to that control.
Start safely
Start with the separate sandbox base URL and confirm the account response says environment=sandbox.
Read the API contract and instrument constraints: units, minimum step, price, and available size.
Send a small order with a unique idempotency key and retain the command ID.
Confirm the outcome
Check the command result, order status, fills, and remaining position. In the terminal, Trades shows closed positions; Trade journal provides fill detail.
A partial fill can leave a working remainder. An HTTP response does not prove the full order was filled.
Use the separate production base URL and your account key only after a successful sandbox test.
Common questions
I received HTTP 202. Did the order fill?
A response can acknowledge a command before the full trading outcome is known. Check the command result, orders, fills, and position.
Can I use the same token on both environments?
Use the key and base URL issued for the intended environment. Sandbox and purchased-account credentials are not interchangeable.
You’re done when…
The command result, fills and resulting state confirm what happened on the intended sandbox account.
If this does not match what you see, use Common questions above or contact support with the page and account details.Continue in QATS
Open the relevant screen to follow the steps in this guide.
Tell us where you got stuck. Never share passwords or access keys.