Testing without orders
Available environments
Kraken Spot has no public testnet. The public Futures demo environment has been retired. In this SDK, testnet: true rejects the retired environment rather than selecting a usable test service. Production remains the default.
Test without placing orders
Use public market-data requests and public streams to check connectivity without account credentials.
For authenticated Spot order checks, use validate: true as shown in Order validation. This sends a real authenticated validation request to production without submitting the order to the market. It requires production Spot credentials and appropriate permissions; it does not use fake funds or a sandbox account.
Coverage and limitations
Order validation checks a request, not execution. It does not simulate fills, partial fills, cancellation races or a full order lifecycle. Use local fixtures and application tests for those paths, while recognizing that fixtures cannot prove live behavior. Never remove validate: true merely to make a test pass: doing so can place a real order.
What these environments can prove
Use test environments to check request formats, credentials, order handling and reconnect recovery within the features they support. Testnet liquidity, prices, fills, fees and availability can differ substantially from production. Accounts, balances and order history may also be reset.
Testnet is not a reliable place to evaluate strategy performance. Demo trading may use production market data, but simulated fills do not establish live profitability, slippage, execution quality or capacity. Treat both as integration tests, not evidence that a strategy will succeed with real funds. See the CEX testnet overview for the distinction between testnet and demo trading.
Before switching environments
- Keep credentials and configuration separate for each account, product and environment. Never fall back to live credentials when a test key is missing.
- Configure every REST, subscription and WebSocket API client separately. Changing one client does not reconfigure another.
- Check the selected environment's supported endpoints and instruments before sending a request. Similar method signatures do not imply identical availability.
- Keep authenticated requests on your server. Confirm the destination and account before enabling any write operation.
Production remains the default. Selecting a test environment is an explicit choice for each client; it is not a global SDK setting.