Binance testnet: testing Autoview before you trade live
Binance runs a free, public spot testnet at testnet.binance.vision, a genuinely separate environment funded with virtual balances instead of real money, and Autoview connects to it as its own exchange option, Binance Testnet, priced at $0. If you want to prove a new alert or a new command works before it touches real funds, this is the account to connect first.
Binance Testnet is a separate account, not a mode inside your live account. You register a new account at testnet.binance.vision and generate its API key there, entirely apart from your live Binance login.
What Binance Testnet is
Binance's spot testnet is a genuinely separate exchange, reachable at testnet.binance.vision rather than the live binance.com. Registering there creates a new account, auto-funded with virtual balances across a range of assets, so you can place orders that look and behave like real fills without risking anything. Those funds aren't real, can't be moved anywhere, and Binance resets the testnet to a blank state roughly once a month, without advance notice, so don't build a long-running test around a balance you expect to stay put.
On Autoview, this shows up as its own exchange connection, Binance Testnet, priced at $0. It's a first-class connection, not a setting on your live Binance account -- you add it separately, with its own API key, and it can run alongside your live Binance connection or entirely on its own.
Register the testnet account and generate its API key
Two steps happen on Binance before you touch Autoview:
- Go to
testnet.binance.visionand log in or register. It's separate from any live Binance account you already have -- there's nothing to link or import. - Once you're in, generate a new API key from the testnet site itself.
This separation matters more than it sounds like it should. A live Binance API key was never issued for the testnet environment, so it doesn't authenticate against testnet.binance.vision. If your connection fails, the first thing to check is whether the key actually came from the testnet site rather than your live account's API Management page.
Binance shows the Secret only once on generation, so copy both the API Key and the Secret before you leave the screen.
Label the testnet key so it can't get mixed up with your live key later. When you save it, whether that's in a password manager or just the connection nickname you give it in Autoview, mark it clearly as testnet. A test key and a live key that look alike in a saved-credentials list is how people accidentally point a live connection at the wrong account, or vice versa.
Connect it to Autoview
In Autoview, add an account and choose Binance Testnet from the exchange list rather than Binance. The form asks for the same two fields as a live Binance connection:
- API Key: the public half the testnet site displayed.
- Secret: the private half it showed only once.
Paste the testnet key's two values in, save, and run the connection test. A clean test means the testnet key authenticated against the testnet environment.
Sending commands: what changes, what doesn't
The command syntax is identical to live Binance. Symbols, order types, and sizing all work the same way as the live Binance setup describes, right down to spot's b=buy/b=sell versus margin's b=long/b=short; only the account and the funds behind it differ.
The one thing that changes is how the Chrome extension picks the exchange. On the webhook platform, a webhook is already tied to whichever account you connected it to, so you never set an exchange in the command itself. On the extension, swap e=binance for e=BINANCETESTNET (or the equivalent e=BINANCE-TESTNET):
| Live Binance (extension) | Binance Testnet (extension) |
|---|---|
e=binance s=BTCUSDT b=buy p=-5% q=1 | e=BINANCETESTNET s=BTCUSDT b=buy p=-5% q=1 |
Add d=1 to any command first, on testnet the same as live, and Autoview parses it and reports what it would have done without placing anything. Worth doing even on testnet funds, since it's the fastest way to confirm the resolved order matches what you meant before you check it against the fill on Binance's testnet.
A clean result from Autoview, an HTTP 200 or a parsed command with no errors, only confirms Binance accepted the request. It doesn't confirm the order filled at a price you'd recognize from live trading. Testnet liquidity and pricing are thinner and less realistic than the live order book, so treat a working testnet order as proof your command and wiring are correct, not as a preview of what a fill will look like on live Binance.
Once testnet looks right
A working Binance Testnet connection proves your command syntax and your alert wiring. It doesn't carry over to your live account's own API key or permissions -- those live on the regular Binance site, so you'll still walk through the live setup on its own terms. When you're ready, follow the getting started with Binance guide to create a live API key and run the same dry-run-then-live check at a small size. Trading Binance's USDT-margined perpetuals instead of spot? See Binance Futures Testnet, a separate testnet with its own endpoint and its own keys.