Getting started with Crypto.com on Autoview
By the end of this guide your Crypto.com account is connected to Autoview, your API keys are saved and tested, and you've put one real order on the book and cancelled it. The test is the part people skip. A dry run proves your alert text parses. Only a live order proves the whole chain works, from alert to fill.
One more thing before we start. Crypto.com is free to connect on Autoview. There's no per-exchange fee for it the way there is for some other live venues, so you can wire it up and trade without a subscription on this connection.
Step 0: Pick your platform
Autoview comes in two forms, and Crypto.com works with both.
- The Chrome extension runs in your browser. It connects directly to TradingView alerts, and it only executes while your computer and Chrome are on.
- The webhook platform runs on our servers. It accepts an HTTP POST from anywhere: TradingView, TrendSpider, a Python script, your own cron job. It executes whether or not a browser is open.
If you want trades to fire while your laptop is closed, use the webhook platform. The guided Crypto.com setup wizard walks the webhook path end to end: save keys, create a webhook, link them, test. The setup below covers both forms. The command syntax differs by a single parameter, and I'll flag it where it does. Compare the two on the platforms page.
Step 1: Create API keys on Crypto.com
API keys are the credentials that let Autoview place orders on your account without ever touching your password. You generate them on the Crypto.com Exchange, not inside Autoview. One thing trips people up here: the Crypto.com Exchange (exchange.crypto.com) is a separate product from the Crypto.com App. API keys come from the Exchange side.
Crypto.com keeps its own walkthrough current, so follow theirs for the exact screens: Crypto.com Exchange API authentication. The short version: sign in at crypto.com/exchange, open Settings then API Keys, and create a new key labelled something like "Autoview".
Two rules are non-negotiable when you create the key:
- Enable trading permission. Autoview needs to place and cancel orders and read your balances. A read-only key will pass the connection test in Step 3, because that test only reads balances, but it will fail the moment an alert tries to trade.
- Leave withdrawal permission off. No automation strategy needs it. A key that can't move funds off the exchange can't drain your account if it ever leaks.
Crypto.com also lets you restrict a key to specific IP addresses. That's worth doing on the webhook platform, where the address is the zone your signals run from. Set the key up first, then come back and whitelist once you know the IP.
Crypto.com shows the Secret Key once, at creation. Copy both the API Key and the Secret Key somewhere safe before you leave that screen. There's no recovering the Secret Key later. You'd revoke the key and make a new one.
Step 2: Add the keys to Autoview
Autoview asks for two fields, and they are labelled to match what Crypto.com gives you: API Key and Secret Key. Paste the API Key into the API Key field and the Secret Key into the Secret Key field. The Secret Key field hides its value by default; there's an eye icon if you want to confirm the paste.
On the extension
Open the extension options, find Crypto.com in the left menu, and click Add account. Paste in the API Key and Secret Key. Leave the key unnamed unless you plan to run more than one Crypto.com key. Naming it means every command has to address it with a=, so skip the name if you only have one.
On the webhook platform
Use the setup wizard. Step 1 saves the API Key and Secret Key and asks you to pick the zone where your commands execute. Then it creates a webhook to receive alerts and links the webhook to these keys. The link is what tells Autoview which credentials to use when an alert arrives. Without it, the webhook answers every alert with "No API Keys linked to this Webhook."
Step 3: Get the symbol format right
Crypto.com names its instruments in two shapes, and the shape depends on the market. Spot pairs use an underscore. Perpetual futures use a hyphen with a -PERP suffix. Get this wrong and the order never reaches the exchange, because Autoview can't match the instrument.
- Spot pair:
BTC_USDT(base, underscore, quote, all uppercase) - Perpetual future:
BTCUSD-PERP(base and quote joined, then-PERP)
A few common instruments, written the way Autoview wants them in the s= symbol:
- Bitcoin / USDT spot:
BTC_USDT - Ethereum / USDT spot:
ETH_USDT - Cronos / USDT spot:
CRO_USDT - Bitcoin perpetual:
BTCUSD-PERP - Ethereum perpetual:
ETHUSD-PERP
If you pass a pair with slashes, Autoview converts them to underscores for you, so BTC/USDT resolves to BTC_USDT. The full instrument list lives in Crypto.com's get-instruments reference. When in doubt, check the exact name there before you send.
Step 4: Fire a dry run, then a real test order
This is the step that saves you a 3am surprise. Do it in two passes.
A real warning before you send anything: Crypto.com is a live exchange. Trades you place through Autoview use your actual Crypto.com balance. There's no separate sandbox order here, so trade at or above the instrument's minimum size, and place a limit order far enough from the market that it won't fill while you're testing.
Pass one, the dry run. Add d=1 to any command. Autoview parses it, shows you exactly what it would have sent, and posts nothing to Crypto.com. A clean dry run for a spot market buy looks like this:
- Extension:
e=cryptocom s=BTC_USDT b=buy q=0.001 t=market d=1 - Webhook:
s=BTC_USDT b=buy q=0.001 t=market d=1
The only difference is e=cryptocom, which tells the extension to route to Crypto.com. On the webhook platform the webhook already knows its exchange, so you leave it out. The dry-run result shows up on your events page exactly like a live trade would. A blue row means it parsed clean. Red or orange means there's an error to fix before you go live.
One parameter is mandatory and worth calling out. Crypto.com orders need an explicit direction in b=. Without it, Autoview stops the command before it ever reaches the exchange. Valid values are b=buy, b=sell, b=long, and b=short. Quantity in q= is in the base currency for spot, so q=0.001 on BTC_USDT means 0.001 BTC; on a perpetual, q= is in contracts.
Pass two, the real order. Once the dry run is clean, drop d=1 and place a resting limit order well away from the market so it won't fill. The p=-5% sets a limit price five percent under the current price:
- Extension:
e=cryptocom s=BTC_USDT b=buy p=-5% q=0.001 - Webhook:
s=BTC_USDT b=buy p=-5% q=0.001
Fire it, then open your Autoview events page and your Crypto.com open orders. You should see the same resting limit order in both. Now cancel it:
- Extension:
e=cryptocom s=BTC_USDT c=order - Webhook:
s=BTC_USDT c=order
Order placed, order seen on Crypto.com, order cancelled, all confirmed in your events log. That's the full round trip. Your setup works.
Step 5: Use live values in real alerts
The examples above hard-code a price offset and a quantity, which is what you want for a controlled test. In real use you'll often want a live value instead. A TradingView alert can write one in: p={{close}} tells TradingView to substitute the candle's close at fire time, and Autoview just receives the number. The {{close}} token belongs to TradingView, not to Autoview. The point is that the alert sender supplies the value. A Python script or another charting platform builds the same command its own way and posts a plain number where {{close}} would sit.
One caution specific to symbols. Don't pipe TradingView's {{ticker}} straight into s=. It hands you strings like BTCUSDT with no underscore, which won't match Crypto.com's BTC_USDT. Hardcode the instrument name, or transform the ticker in your alert text so it comes out in the right shape.
Step 6: Troubleshoot the usual snags
Most first-run problems are one of these.
- Invalid API credentials. Autoview rejects the key. Almost always a typo on paste, or a key created without trading permission. Re-paste both halves and confirm trading is enabled on Crypto.com's side.
- Unknown market symbol. You sent a spot pair without the underscore, or a perpetual without
-PERP. UseBTC_USDTfor spot,BTCUSD-PERPfor perps, and check the exact name in Crypto.com's instrument list. - Invalid Order Book (b=) parameter. You left out the direction. Add
b=buy,b=sell,b=long, orb=short. - Crypto.com rejects the order. The error in your log comes straight from Crypto.com, prefixed with its own code, often because the quantity sat below the instrument's minimum. Bump the size and resend.
When a command behaves oddly, put d=1 back on it. The dry-run output is the fastest way to see what Autoview thinks you asked for versus what you meant.
Connected and tested? That's the working set for Crypto.com on Autoview: market and limit orders across spot and perpetuals, with d=1 there whenever you want to dry-run a command before it fires. Stop-loss, take-profit, trailing, and OCO brackets aren't available on Crypto.com through Autoview right now, so don't write alerts that lean on them yet.