BLACK FRIDAY IS BACKNov 24 to 30. Join the list and get in a day early.Join the list

How to set up the Autoview web platform

Autoview · Guide · Updated July 11, 2026

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.

  1. Log in to your exchange and open its API management section.
  2. Create a new key. Give it a label you'll recognize later.
  3. Enable trading permission. Many exchanges create keys read-only by default, so this is the step people miss.
  4. 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.

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.

The dropdown you pick a webhook from lists every webhook on your account, not just the one you just made in Step 3. If you've connected other exchanges before, their webhooks show up in the same list. Match the name, don't just take whichever one is on top.

Step 5: Build a command

A command is the instruction your alert carries: what to trade, which side, how much. Autoview doesn't have a form-based builder. The syntax is short enough to write by hand once you've seen a few examples: copy a matching line from the command reference and swap in your symbol and size.

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.

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. Not using TradingView? The next section covers the setting to pick in other tools.

Any tool that can send a webhook

TradingView is one sender. Anything that can make an HTTP POST to your webhook URL can place the same orders, with the same commands. What decides whether it works is the body the tool sends and the Content-Type it puts on it.

The three body forms Autoview accepts

  • Plain text. Content-Type text/plain (or any type that isn't JSON or a form), with the command as the body: d=1 b=buy s=BTCUSDT.
  • A JSON string. Content-Type application/json, with the command in quotes: "d=1 b=buy s=BTCUSDT".
  • A JSON object with an alert field. Content-Type application/json, with the command as a string under alert: {"alert": "d=1 b=buy s=BTCUSDT"}.

Anything else is refused. Form-encoded and multipart bodies get a 415. A JSON object without a string alert field gets a 400, and the error message names the shapes that are accepted. The label has to match the body, too: JSON sent as text/plain is read as raw command text, braces and all, so it won't be unwrapped. Pick the content type that matches what you're sending.

Securing it with ?key=

If your webhook has a key, add ?key=yourkey to the end of the URL, or start the body text with the key. With a JSON body, the key goes at the start of the command string, not before the opening brace. A request with the wrong key is rejected and the rejection shows in your Event Log. The webhook key guide covers both methods.

Named senders and the setting to pick

  • TradingView. In the alert dialog, turn on the webhook notification, paste your URL, and put the command in the message. Webhooks need a paid TradingView plan with two-factor authentication on. TradingView webhook help
  • TrendSpider. Paste your URL into the webhook box in Account & Settings, or into a Strategy Bot's entry or exit webhook URL. The body is the alert's Description or "Your Note" field, or the bot's Webhook Body. TrendSpider labels a valid JSON body application/json and anything else text/plain, so write plain command text or {"alert": "..."}. TrendSpider webhooks help
  • Zapier. Use the Webhooks by Zapier POST action. Set Payload Type to json and add one Data row with the key alert and your command as the value. Don't pick form, which Autoview rejects. Webhooks by Zapier needs a paid Zapier plan. Zapier webhooks help
  • n8n. In the HTTP Request node, set Method to POST and turn on Send Body. Choose Body Content Type JSON with a body parameter named alert, or Raw with Content Type text/plain. Form URLencoded and Form-Data won't work. n8n HTTP Request docs
  • IFTTT. In the Webhooks service, use the "Make a web request" action with Method POST. Set Content Type yourself to text/plain or application/json; IFTTT doesn't document what it sends when the field is left empty, and application/x-www-form-urlencoded gets a 415. The Webhooks service needs IFTTT Pro. IFTTT web request action
  • Make. In the HTTP app's "Make a request" module, set Body content type to application/JSON with {"alert": "..."}, or to Custom with the content type value text/plain. Not form-urlencoded or multipart. Make HTTP app docs
  • Your own script, or curl. Set the Content-Type header yourself rather than trusting a library default, which is often form-encoded. Examples for curl, Python and Node are on the custom webhooks page.
  • An AI agent. An agent that POSTs to your webhook URL follows exactly the same rules as a script. More on agents below.

A dry-run test from curl looks like this:

curl -X POST "https://api.autoview.com/hook/<identifier>/?key=yourkey" \
  -H "Content-Type: text/plain" \
  -d "d=1 b=buy s=BTCUSDT"

A tool that can only post its own fixed JSON layout, or form data, won't work until Autoview parses that shape. Before you build on a new sender, check that it lets you write the body and choose the content type.

AI agents: webhook or MCP

There are two different ways an agent can trade through Autoview, and they cover different exchanges.

  • The webhook path. The agent POSTs a command to your webhook URL, like any sender above. It works on every exchange your webhook is linked to.
  • The MCP path. Autoview's MCP server lets an agent place orders directly through its tools, with no webhook in between. Live MCP trading covers Kraken and Crypto.com only. The other MCP venues are practice accounts: OANDA Practice, Crypto.com Demo, Bybit testnet and Tradovate simulation. See getting started with MCP.

For live trading on any other exchange, an agent uses the webhook path.

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.

The Autoview log shows what Autoview sent and what the exchange returned to it, and that is not a substitute for looking at the exchange itself. After your first live order, open the exchange's own order history or position screen and confirm the fill independently. That is the only way to know the order did what you intended, not just that Autoview reported success.

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.

See supported exchanges