Getting started with Binance.US
By the end of this guide your Binance.US account is connected to Autoview, your API credentials carry the right permissions, and you have placed one small test order and cancelled it. Binance.US is a separate, US-regulated exchange from Binance.com, its own company with its own account system and its own API, so treat this guide as Binance.US-specific rather than a stand-in for the generic Binance guide.
One thing to know before you start: Binance.US has no free demo or testnet account. Every connection, and every order sent through it, touches your real Binance.US account. That changes how you should run the test step below, and this guide is built around that fact.
Step 1: pick how Autoview runs
Autoview executes through two surfaces, and your Binance.US connection lives on whichever one you choose.
- Chrome extension. Runs in your browser. Chrome and your computer need to stay open for an order to fire, and it reads TradingView alerts directly.
- Webhook platform. Runs on Autoview's servers. Your laptop can be closed and orders still go out, and it accepts a POST from any source, TradingView included.
Not sure which one? Start with the webhook platform. It does not care whether your machine is awake. Compare both on the platforms page.
Step 2: create API credentials on Binance.US
API credentials are what let Autoview place orders on your Binance.US account without ever touching your password. You generate them inside Binance.US, under its API management screen, not inside Autoview. Binance.US hands you two pieces: an API Key and a Secret. Copy both somewhere safe before you leave the page. Autoview signs every trading request with the Secret; it never sends the Secret itself over the wire.
Two rules when you create the key:
- Grant trading permission. Autoview needs to place and cancel orders and read your balances. Without it, nothing executes.
- Never grant withdrawal permission. No automation strategy needs it, and a key that cannot move funds off Binance.US cannot drain your account if the key ever leaks.
There is no separate testnet key to generate here. Whatever key you create talks to the same live Binance.US account.
Step 3: add the credentials to Autoview
- On the extension: open the extension options, find Binance.US in the left menu, and click Add account. Paste in the API Key and Secret. Leave the connection unnamed unless you plan to run more than one Binance.US key.
- On the webhook platform: log in to Autoview, open the Binance.US configuration, and enter the API Key and Secret there. Naming the connection is what lets you wire it to a specific webhook later, so a clear name is worth it here. Save, and watch for the confirmation that the account connected.
Step 4: place a small test order, then cancel it
This is the step that proves the connection, and because Binance.US has no demo account, run it carefully. Start with a dry run: add d=1 to any command and Autoview parses it and logs exactly what it would have sent, but nothing reaches Binance.US. Get a clean dry run before you send anything real.
For the real test, keep the size at or near Binance.US's minimum for the pair, and price the order well away from the market so it rests instead of filling while you are still confirming the connection. Use Binance.US's own pair symbol in s=, written the way Binance.US writes it, with no separator, for example BTCUSD rather than BTC/USD.
Place a limit buy
- Extension:
e=binanceus s=btcusd b=buy p=-5% q=0.001 - Webhook:
s=btcusd b=buy p=-5% q=0.001
Reading it left to right: trade on your Binance.US connection, symbol BTCUSD, buy side, limit price five percent below the current price, a small quantity. Check the Autoview log and your Binance.US order screen. You should see one open limit order.
Cancel it
- Extension:
e=binanceus s=btcusd c=order - Webhook:
s=btcusd c=order
Confirm the order disappears from both the Autoview log and your Binance.US account. Placed, then cancelled, both confirmed. That is the full round trip, and your connection is sound.
Three Binance.US quirks worth knowing before you build a real strategy
Spot only, no margin. Autoview's Binance.US connection trades your regular spot balance. There is no long or short side backed by margin here, only a plain buy or sell against what is already in your account.
A single order cannot carry both a stop-loss and a take-profit. Binance.US rejects that combination outright. Send your entry, then send the stop-loss and the take-profit as two separate alerts once the entry fills, rather than trying to attach both to one order.
Trailing stops are supported. Binance.US does not have a standalone trailing-stop order type, so Autoview rides your trailing distance on Binance.US's own trailing delta, a fixed basis-point offset attached to a stop order, so the stop follows price by that set distance.
If something goes wrong
- Order rejected on syntax. Re-run with
d=1and read the log line by line. It tells you exactly how Autoview interpreted every parameter you sent. - Invalid API credentials. Almost always a typo on paste, or a key created without trading permission. Re-paste both the API Key and Secret and confirm the permission on Binance.US's side.
- Binance.US rejects the order. The error in your log comes straight from Binance.US, most often because the order's value sits below Binance.US's minimum for the pair, or the symbol is wrong. Confirm the symbol and bump the size.
- Account shows disconnected. Nothing executes while it does. Re-check the key and re-add it if needed.
Next steps
Connection tested and working? From here you can build out the commands that make automation worth running: limit and market orders sized off your account balance, stop-loss and take-profit sent as separate alerts, and a trailing stop riding Binance.US's trailing delta. Build each one the same way you built the test, write it, dry-run it with d=1, then let it fire for real, in small size first.