How to test a Crypto.com strategy before going live
You built a Crypto.com strategy and you want it to trade on its own. What you will not do is point automation at real funds before you have watched it behave. That is the right instinct. This page answers three things: whether you can use a Crypto.com demo account with Autoview, why not, and how to test a Crypto.com strategy safely anyway.
The short answer: no demo account to pick today
There is no Crypto.com demo account you can connect through Autoview today. When you add a connection, Crypto.com is offered as a live account only.
You may see a Crypto.com Demo integration mentioned elsewhere, and it does exist in Autoview's code. It points at Crypto.com's UAT sandbox instead of the production exchange. It is not offered when you add a connection, though, and almost nobody could use it anyway, because of the keys it needs.
Why: Crypto.com gates its own sandbox
Per Crypto.com's own documentation, UAT environment access is by invitation only for institutional accounts. Obtaining those credentials is Crypto.com's decision, not ours, and a retail trader usually cannot get them at all. Crypto.com does not publish a self-serve way to request UAT access, so I will not invent one for you. The rest of this page gives you ways to test that need no invite.
How automating Crypto.com works
Three pieces sit in a line. Your signal decides, Crypto.com executes, and Autoview is the bridge between them. The signal can come from anything that sends a webhook. TradingView is the sender most Crypto.com traders reach for, since that is where they already chart, but it is not the only one. A script or another platform slots in exactly the same way.
On the webhook platform, the webhook decides where an order lands, not the command. A webhook sends every command to each exchange account linked to it, so link your demo connection to one webhook and your live connection to another. On the Chrome extension, e=CRYPTODEMO (or e=CRYPTO-DEMO) means demo and e=CRYPTO or e=CRYPTOCOM means live, and a= picks the saved account. On a webhook, e= is accepted but ignored. Symbols are written Crypto.com's way, in underscore form like BTC_USD. Autoview converts a slash to an underscore and matches the result against Crypto.com's instrument list, and it rejects anything it cannot find rather than guessing. The command reference has the full token syntax.
Test safely, sandbox or no sandbox
This is the section that matters most, because it works whether or not you ever see a Crypto.com sandbox.
Add d=1 to a single command and Autoview disables it: it parses the command and reports exactly what it would have done, without placing an order. That is a dry run, and it works on any connection, live included. There is no account-wide switch for this on the cloud platform, so put d=1 on every command line you are testing -- it only covers the line it's on. If you want a true safety net instead of a per-line flag, fire the same commands at a demo or testnet connection.
One default is worth knowing before you go live. Leave the quantity token q= off a command and Autoview uses 100% of the account balance, so set q= explicitly on any real order. And if you cannot get Crypto.com UAT access, you are not stuck. Autoview supports open testnets on other venues you can reach today, among them OKX demo, Binance testnet, Bybit testnet, Deribit testnet, and Gemini sandbox. An OKX demo account is one you can open now and practice the same command syntax on.
What a dry run does and does not prove
A dry run is honest about one thing. It confirms the command is wired correctly and shows the exact field mapping Autoview will send. Run e=CRYPTO s=BTC_USD b=sell t=market q=0.00005 d=1 and Autoview resolves it to {"instrument_name":"BTC_USD","quantity":"0.00005","side":"SELL","type":"MARKET"}. That is a field-mapping confirmation, not a live fill acknowledgment. It does not by itself prove live fills, live pricing, or the slippage you will actually get.
A few operational facts you will meet either way. Crypto.com limits API access to 10 calls per URL per second, and a request over that comes back as HTTP 429. New Crypto.com API keys are read-only by default, so enabling trading requires whitelisting an IP address first. When Crypto.com rejects a request, Autoview passes its own numeric error code and message straight through, unchanged, so the failure stays legible in your Autoview events log.
Start here
Start on the safe path. Connect Crypto.com, dry-run a command with d=1, and read back what Autoview would have sent. Then place one small limit order far from the market and cancel it, which proves the whole chain without risking a fill. The Crypto.com setup guide walks through the actual connection and that test order.
Autoview automates more than crypto. Forex through OANDA, futures through Tradovate, stocks through Alpaca, and more than a dozen crypto exchanges, all from one alerting workflow. Thousands of verified accounts run on it, and trade webhooks flow around the clock. Crypto.com is one of them.