What is Autoview, and how do you trade with it?
By the end of this guide you'll know exactly what Autoview does and you'll have fired one test order at an exchange without risking a cent. That's the goal. Read the orientation first, then follow the steps in order.
Here's the short of it. You have a strategy that decides when to buy and sell. Autoview is the piece that takes that decision and turns it into a real order on your broker or exchange. No watching the screen, no clicking buttons at 3am.
What Autoview actually is
Autoview is a bridge. On one side sits whatever generates your signals. On the other sits your live trading account. When a signal fires, Autoview reads the command inside it and places the matching order. That's the whole job, and it does it the same way every time, which is the entire point of automating.
Most people send signals from TradingView. You don't have to. The webhook platform accepts a POST from anything that can send one. TrendSpider, a custom Python script, your own server. TradingView is one sender among many. The Chrome extension is the part that's wired specifically to TradingView alerts.
Pick your platform: extension or webhook
There are two ways to connect your alerts to your exchange. Same integrations, same command syntax. The difference is where the work happens.
- The webhook platform. Runs on our servers. You generate a private webhook URL, point your alerts at it, and orders go through whether or not your computer is on. This is the one most people want, and it's the one that works cleanly with TradingView, TrendSpider, or any custom script.
- The Chrome extension. Runs inside your browser and reads TradingView alerts directly. Your keys live in the browser's local storage, not on a server. The trade-off is real: Chrome has to be open and running for it to execute. Close the laptop, nothing fires.
My honest take? Start with the webhook platform unless you have a specific reason to keep keys off-server. If you want the full breakdown, the side-by-side comparison lays both out.
Step 1: Connect your exchange with API keys
Autoview can't place orders until you give it permission. You do that with API keys: credentials you create on your exchange that grant a specific, limited set of powers to an outside app.
Create the keys on your exchange's own site, then paste the credentials into Autoview (a key and secret on most exchanges; OANDA uses an Account ID and Access Token). Each exchange's key screen looks a little different, so follow the exchange's own documentation for where the button lives and what the permissions are called.
Two rules that matter more than anything else on this page:
- Grant trading and read-only account access. Nothing more. Autoview needs to place and cancel orders and read your balances and positions. That's it.
- Never grant withdrawal permission. No automation tool should be able to move money off your account. If the exchange offers a withdrawal toggle on the key, leave it off.
If your exchange supports IP whitelisting, turn it on. It locks the key so it only works from approved addresses. Your exchange documents whether the feature exists and which addresses to allow.
Step 2: Write the command your alert will send
An Autoview command is a short string of parameters that tells it what to do. A basic market buy reads like this:
s=EURUSD b=buy q=1 t=market
Symbol, direction, quantity, order type. From there you can layer on the parts that do real risk management: take-profit and stop-loss levels, reduce-only orders, trailing stops, limit prices. Those are documented in the alert syntax reference. Build up to them once the basics fire cleanly.
The values above are hardcoded. You can also feed in a live value, like a limit price pulled from the candle:
s=EURUSD b=buy q=1 t=limit p={{close}}
One thing trips people up here. {{close}} is not Autoview syntax. It's a TradingView placeholder, and TradingView swaps in the real number when the alert fires. The sender supplies the value. Send from a Python script or another platform and you'd insert the price its own way. Autoview just reads whatever number arrives.
One symbol gotcha worth catching early
Symbol format is per-exchange, and OANDA is the one that trips people up. OANDA instrument names use an underscore, all uppercase: base, underscore, quote. So it's EUR_USD, not EURUSD. Send EURUSD and OANDA rejects it. Hardcode the underscore version in your alert and you'll save yourself a confusing afternoon.
Step 3: Dry-run it before you risk anything
This is the step people skip and regret. Before any real capital touches an order, add d=1 to your command:
s=EURUSD b=buy q=1 t=market d=1
The d=1 flag disables live sending, so it behaves as a dry run. Autoview reads the command, works out exactly what it would do, and writes that to your logs. It does not send the order to the exchange. That's how you confirm the syntax is right with zero risk. Read the log line. Does it match what you meant? Good.
Step 4: Place one tiny live order
Dry runs prove the syntax. They don't prove the full path to your exchange. So once the log looks right, drop the d=1 and fire a single small order, just above the exchange's minimum size, then cancel it.
You're checking the whole chain end to end: alert fires, Autoview parses it, the order lands on your account. If you'd rather not use real money at all yet, connect a demo or testnet account first. Several of those connections are free, so you can watch a fill happen without funding anything.
Verify and troubleshoot
Almost every problem shows up in the logs, so read them first.
- Nothing happened. Check the alert actually reached Autoview. With the extension, Chrome has to be open. With the webhook platform, confirm the alert is POSTing to your exact webhook URL.
- The exchange rejected the order. Usually symbol format (see the OANDA note above) or size below the exchange minimum. The log shows the exchange's own error.
- Permission errors. Re-check the API key has trading and read access, and that you didn't accidentally paste an expired or trimmed secret.
- Want to know if it's us or you? The status page shows whether the platform is healthy.
A little history, since people ask
Autoview started as a Chrome extension, a direct browser link for TradingView alerts. When Google migrated extensions from Manifest V2 to V3, the old listing was retired along with countless others. Autoview rebuilt on V3, and the extension is live on the Chrome Web Store today. The webhook platform came later, for traders who needed execution that doesn't depend on a browser being open. Both run now.
Autoview connects to a wide spread of markets, not just crypto: forex through OANDA, futures through Tradovate, stocks through Alpaca, and 20-plus crypto exchanges including Crypto.com, Kraken, Bybit, OKX, and Coinbase. One alerting source, many destinations.
That's the whole workflow. Connect keys, write a command, dry-run it, place one small live order, watch the logs. Do that once and you've automated a trade.