Getting started with Bybit on Autoview
By the end of this guide your Bybit account is connected to Autoview, your API key carries the right permissions, and you've placed one real test order and cancelled it. That last part is the point. A dry run proves your syntax parses. Only a live order proves the whole chain works.
What Autoview does
Autoview turns an alert into a trade. You connect your Bybit account once with an API key. After that, an alert fires a command, and Autoview places the order on Bybit for you.
The work happens in a webhook on our servers. That webhook runs around the clock and accepts a POST from anywhere: TradingView, TrendSpider, a Python script, your own cron job. TradingView is the common sender, not the only one. Nothing has to stay open on your machine for a signal to execute.
Create your API key on Bybit
An API key is the credential that lets Autoview trade on your account without ever seeing your password. You generate it inside Bybit, not inside Autoview. Bybit keeps its own walkthrough current, so create the key from your API management page: Bybit API management.
When you create the key, pick the System-generated path (the API Transaction option), not the third-party connect flow. The connect flow expects an OAuth handshake Autoview does not use. Then two rules:
- Grant order permissions. Autoview needs to place and cancel orders and read your balances and positions. Under a Unified Trading account that's the Trade scope; on contract accounts it's the Orders and Positions scope. Without it, nothing executes.
- Never grant withdrawal permission. No automation needs it. A key that can't move funds off Bybit is a key that can't drain your account if it leaks.
Bybit also lets you whitelist IP addresses, so a key only works from an address you approve. On the webhook platform that address is the zone your signals run from. Autoview shows it to you when you add the key, so set the key up first and come back to whitelist once you know the IP.
Bybit shows the secret once, at creation. Copy both the key and the secret somewhere safe before you leave that screen. There's no recovering the secret later. You'd just delete the key and make a new one.
Add the keys to Autoview
Open Autoview, find Bybit in the exchange list, and add an account. Autoview asks for exactly two values:
- API Key: the public half Bybit generated.
- Private Key: the secret half. Bybit calls this your API secret on its own screen; Autoview labels the field Private Key. Same value, paste it here.
There's no passphrase for Bybit, so two fields are all you'll see. Paste both, then run the connection test. A clean test means the key authenticates. If you plan to run more than one Bybit key, name each one so you can address it later; with a single key you can leave it unnamed.
Fire a dry run, then a live test
This is the step people skip, and then they wonder at 3am why a live signal did nothing. Don't skip it.
A real warning before you send anything: Bybit commands hit your live account. Trade a size at or above Bybit's minimum for the symbol, 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 Bybit. Get a clean dry run before you send a live one.
Bybit symbols are concatenated and uppercase, with no separator: BTCUSDT, ETHUSDT. This e=bybit connection trades inverse and linear perpetuals only, so BTCUSDT resolves to the USDT perpetual. Bybit spot is a separate connection (e=bybit-spot); connect that if you want to trade spot pairs. A limit buy 5 percent under the market looks like this:
- Extension:
e=bybit s=BTCUSDT b=buy p=-5% q=1 - Webhook:
s=BTCUSDT b=buy p=-5% q=1
The only difference is e=bybit, 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 hard-codes a price offset and a quantity, 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 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 Bybit orders. You should see the resting limit order in both. Now cancel it:
- Extension:
e=bybit s=BTCUSDT c=order - Webhook:
s=BTCUSDT c=order
Order placed, order cancelled, both confirmed in the log and on Bybit. That's the full round trip.
Go live
Connected and tested? Good. A few snags catch most people on the first run.
- Sign error or invalid key. Bybit rejects the credentials. Almost always a paste typo on the Private Key, or a key created without order permission. Re-paste both halves and confirm the scope on Bybit's side.
- Account shows disconnected. Nothing executes while it does. Re-check the key, and if you whitelisted an IP, confirm the address Autoview sends from matches the one you approved.
- Bybit rejects the order. The error in your log comes straight from Bybit, often because the quantity sat below the symbol's minimum. 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. From here you'll want stop-loss, take-profit, and trailing parameters layered onto these same commands. That's where the automation gets interesting.