How to set up the Autoview web platform
By the end of this guide you'll have a working automation: an alert lands at your private Autoview URL, Autoview reads the command, and the order goes to your exchange. No browser tab open, no machine running at home. The webhook does the work.
This is the platform path, not the Chrome extension. The extension reads TradingView in a browser. The web platform is different and, for most people, better: it takes a webhook from anything that can POST to a URL. TradingView is the common sender. So are TrendSpider, a Python script, or your own server. The platform doesn't care where the alert came from, only that it arrived.
Five pieces connect in order. Exchange keys, a webhook, a link between them, a command, and an alert that carries it. Let's build them.
Before you start
You need an Autoview account and an account on a supported exchange. Make a free account if you don't have one. On the exchange side, Autoview covers forex through OANDA, futures through Tradovate, stocks through Alpaca, and 20-plus crypto exchanges including Crypto.com, Kraken, Bybit, OKX, and Coinbase. The pricing page lists what's live.
If you're new to all of this, point your first setup at a demo or testnet connection. Several of those are free, and you can watch a fill happen end to end without real money on the line.
Step 1: Create API keys on your exchange
The platform executes trades through your exchange's API, so it needs a key. You generate that key on the exchange, not on Autoview.
- Log in to your exchange and open its API management section.
- Create a new key. Give it a label you'll recognize later.
- Enable trading permission. Many exchanges create keys read-only by default, so this is the step people miss.
- Do not enable withdrawals. An automation key has no business moving funds off the exchange. If the exchange offers IP whitelisting, use it.
Exchanges differ in where these settings live and what they call them. Follow the exchange's own API documentation for the exact clicks. Copy the API key and secret somewhere safe. The secret is usually shown once.
Step 2: Add the keys to Autoview
In your Autoview dashboard, open the API Keys page and click Set Up Exchange. That starts the guided setup for the exchange you're connecting, which walks you through pasting the key and secret from Step 1 and naming the connection. Save, and the connection shows up in your list.
Step 3: Create a webhook
A webhook is the private inbox your alerts post to. Open the webhooks section and create one. Name it after the strategy or signal source you'll point at it.
You can add an optional key to the webhook. A key is a shared secret a request has to carry, so anything without it gets ignored. You can send it two ways: appended to the URL as ?key=yourkey, or as the first thing in the alert message body, where Autoview strips it before reading your commands. The message-body form helps when your alert sender can't add query parameters to the URL. It's worth setting. A webhook URL is a long random string, but it's still a URL someone could stumble onto, and the key stops a stray request from triggering a trade.
After you create the webhook, Autoview gives you the URL to copy. That URL is what you paste into your alert provider in Step 6. Keep it private. Anyone who has it can send your account a command.
Step 4: Link the webhook to your API keys
A fresh webhook isn't wired to anything yet. The link is what tells Autoview "alerts arriving here should execute on this exchange connection." In the linkage section, create a link, pick the webhook from Step 3 and the API connection from Step 2, and save.
One webhook can drive one connection or several. If you link two exchanges to the same webhook, one alert fans out to both. Useful, and also easy to forget you did. Check the link before you go live.
Step 5: Build a command
A command is the instruction your alert carries: what to trade, which side, how much. Autoview has a Command Builder that walks you through it with a short questionnaire and hands back the text to drop into your alert. Use it. The syntax is compact and the builder keeps you from guessing.
One symbol detail trips up forex traders specifically. OANDA wants instruments in underscored form, like EUR_USD, not EURUSD. Send the wrong format and the order won't fill. Match whatever symbol format your exchange uses, and the builder will reflect it.
Before any of this touches real capital, add the dry-run flag d=1 to your command. With d=1, Autoview parses the alert and shows you exactly what order it would have placed, without sending it. It's the cheapest way to confirm your syntax is right.
Step 6: Send the alert from your platform
Now connect the sender. In TradingView, this lives in the alert dialog under notifications: turn on the webhook option and paste your Autoview webhook URL from Step 3. Put your command from Step 5 in the alert's message body. Other senders work the same way at heart, post the URL with the command in the payload.
Save the alert. If your platform has a "test" button for webhooks, use it before you trust live signals.
Verify it worked
Open the event log in your Autoview dashboard. This is where every received alert and its result show up, and it's the first place to look when something seems off.
- In dry-run (
d=1), the log shows the order Autoview would have sent to the exchange. Read it. Is the symbol right? The side? The size? - Live, the log shows the order plus the exchange's actual response.
If the log shows nothing after a test alert, the alert never arrived, so check the webhook URL in your sender and the key. If a connection reads as disconnected, the API key is almost always the cause, so revisit Step 1 and confirm trading permission is on.
Troubleshooting the usual suspects
Nothing in the event log
The alert didn't reach Autoview. Confirm the webhook URL is pasted correctly and, if you set a key, that it's included. Re-fire the test from your sender.
Order rejected by the exchange
The alert arrived but the exchange refused it. The log carries the exchange's response, which usually says why. Common culprits: wrong symbol format (see the OANDA EUR_USD note), a size the account can't support, or an API key without trading permission.
Connection shows disconnected
Re-check the API key on the exchange. Keys expire, get revoked, or were created read-only. Generate a fresh one and add it again in Step 2.
That's the whole loop. Keys, webhook, link, command, alert, log. Once a dry run reads clean, flip to live and let the platform handle execution while you do something else.