Getting started with Binance on Autoview

Autoview

By the end of this guide your Binance account is connected to Autoview, your API credentials carry the right permissions, and you've fired one test order and cancelled it. That last part matters. A dry run tells you your syntax parses. Only a real order tells you the whole chain works, and Binance gives you a free way to run that real order without risking a cent.

One decision up front: live Binance or Binance's testnet. Everything below works the same on both.

Step 0: Pick your platform

Autoview comes in two forms, and Binance 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 a POST from anywhere: TradingView, TrendSpider, a Python script, your own cron job. It executes whether or not any browser is open.

If you want trades to fire while your laptop is closed, use the webhook platform. If you're tied to the extension's live TradingView link, use the extension. The setup below covers both; the command syntax differs by a single parameter, and I'll flag it where it does. Compare them side by side on the platforms page.

Step 1: Create API credentials on Binance

API credentials are what let Autoview place orders on your account without ever touching your password. You generate them inside Binance, not inside Autoview, under API Management. If you want to test first, Binance runs a full separate testnet at testnet.binance.vision with its own account and its own keys; nothing you do there touches your live balance.

When you create the key, two rules are non-negotiable:

  • Grant spot trading permission. Autoview needs to place and cancel orders, and read your balances and open positions. Without it, nothing executes.
  • Never grant withdrawal permission. No automation strategy needs it, and a key that can't move funds off the exchange is a key that can't drain your account if it leaks.

Binance calls the two pieces you'll paste into Autoview API Key and Secret. Copy both somewhere safe before you leave the page. If you lose the Secret, delete the key and generate a new one; Binance doesn't show it to you twice.

Step 2: Add the credentials to Autoview

Same credentials, slightly different door depending on your platform.

On the extension

Open the extension options, find Binance in the left menu, and click Add account. Paste in the API Key and Secret. Leave the key unnamed unless you plan to run more than one Binance 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

Log in, open the Binance configuration, and enter the API Key and Secret there. Here, naming the key is what lets you wire it to a specific webhook later, so a clear name is worth it. Save, and watch for the confirmation that the account connected.

Testing on testnet.binance.vision? Add it as a separate Binance Testnet connection, not your regular Binance one. The two are distinct accounts in Autoview, matching the two separate accounts Binance keeps on its side.

Step 3: Fire a test order, then cancel it

This is the step people skip, and then they wonder why a live signal did nothing. Don't skip it, and if you're on testnet there's no reason not to run it exactly like a live order.

A note if you're on the live account: Binance has no separate sandbox for a live key, so trade a size at or above Binance's minimum notional for the pair, and place a limit order far enough from the market that it won't fill while you're testing.

Start with a dry run. Add d=1 to any command and Autoview parses it, shows you exactly what it would have done, and sends nothing to Binance. Get a clean dry run before you send a live one.

Then send the real thing. The cleanest trigger is a single-fire TradingView alert on an active market; a condition like "price greater than 0" fires it almost instantly. Use Binance's own pair symbol in the s= parameter, written the way Binance writes it, with no separator: BTCUSDT, not BTC/USDT. A limit buy 5% under the market looks like this:

  • Extension: e=binance s=<BINANCE_PAIR> b=buy p=-5% q=1
  • Webhook: s=<BINANCE_PAIR> b=buy p=-5% q=1

The only difference is e=binance, which tells the extension which exchange to route to. On the webhook platform the webhook already knows its exchange, so you leave it out.

The example above hard-codes a price offset, 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 is TradingView's, not Autoview's. The point is that the alert sender supplies the value, so a Python script or another platform builds the same command its own way and posts a plain number where {{close}} would sit.

Fire it, then open the Autoview log and your Binance orders. You should see the resting limit order in both. Now cancel it:

  • Extension: e=binance s=<BINANCE_PAIR> c=order
  • Webhook: s=<BINANCE_PAIR> c=order

Order placed, order cancelled, both confirmed in the log and on Binance. That's the full round trip. Your setup works.

Two Binance quirks worth knowing before you build a real strategy

Spot and margin read the same b= parameter differently. b=buy and b=sell trade your Binance spot wallet. b=long and b=short route the same command to Binance margin instead, cross by default, and Autoview also supports Binance's isolated margin per pair. If you only trade spot, buy and sell are all you need; margin only activates when you reach for long or short.

A single order can't carry both a stop-loss and a take-profit. Binance rejects that combination outright. Send an entry with one protective leg using Binance's native OCO order, or send the stop-loss and take-profit as two separate alerts. Binance doesn't have a standalone trailing-stop order either; Autoview rides your trailing distance on Binance's own trailing delta, a fixed basis-point offset attached to a stop or OCO leg, so the stop follows price by that set distance rather than a freely configurable trail.

Step 4: Troubleshoot the usual snags

Most first-run problems are one of three things.

  • 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 the permission on Binance's side.
  • Account shows disconnected. Nothing executes while it does. Re-check the key, and confirm you added it under the right connection, Binance or Binance Testnet.
  • Binance rejects the order. The error in your log comes straight from Binance, most often MIN_NOTIONAL because the order's value sat below Binance's minimum for the pair. 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? Good. Next you'll want stop-loss, take-profit, and OCO parameters layered onto these same commands. That's where the automation gets interesting.

Connect Binance