Getting started with Deribit on Autoview
By the end of this guide your Deribit account is connected to Autoview, your API key carries order permission and nothing more, and you've fired one test order and cancelled it. Deribit is where you trade crypto options and perpetuals, so that round trip matters. A dry run proves your syntax parses. A real order proves the whole chain works.
What Autoview does
Autoview executes through a webhook on our servers. The webhook runs around the clock, and it accepts a POST from any sender: a TradingView alert, TrendSpider, a Python script, your own cron job. TradingView is one source of many. When an alert fires, it carries a short command. Autoview reads the command and places the matching order on Deribit through the keys you give it.
So the connection is simple. You create an API key on Deribit, you paste it into Autoview, and from then on your alerts drive the orders. Autoview never sees your password and never needs it.
Deribit also runs a full testnet. If you want to rehearse against fake balances first, connect the Deribit Testnet instead, then switch to live once you trust the flow. The steps are identical; only the account differs.
Create your API key on Deribit
You generate the key inside Deribit, not inside Autoview. Sign in, open your account menu, and find the API section. Deribit keeps its own walkthrough current, so follow theirs for the exact clicks and the latest screen layout: Deribit API documentation.
Add a new key. When you set its scopes, two rules are not negotiable:
- Grant trade permission. Autoview needs to place and cancel orders and read your account balance and open positions. Without trade scope, nothing executes.
- Never grant withdrawal permission. No automation needs it. A key that cannot move funds off Deribit cannot drain your account if it ever leaks.
Deribit gives each key a public half and a private half. Copy both. The private half is shown once, so save it somewhere safe before you leave that screen. There is no recovering it later. You would just delete the key and make a new one.
Add the keys to Autoview
Open the Deribit connection in Autoview. You'll see two fields, and they map straight onto the two halves of your Deribit key:
- Access Key is the public half. Paste it here.
- Access Secret is the private half. Paste it here.
Deribit has no passphrase, so there's no third field to fill. Name the connection if you plan to run more than one Deribit key, since a clear name is what lets you wire it to a specific webhook later. Save, and watch for the confirmation that the account connected. If you're rehearsing first, do the same on the Deribit Testnet connection with a testnet key.
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.
Start with a dry run. Add d=1 to any command. Autoview parses it, shows you exactly what it would have done, and sends nothing to Deribit. Get a clean dry run before you send anything real.
Deribit uses instrument names, not plain pairs. A perpetual looks like BTC-PERPETUAL. A dated future looks like BTC-29DEC23. An option looks like BTC-29DEC23-30000-C. Spot looks like BTC_USDC. Use the exact instrument name in the s= symbol, and check it on Deribit before you send. A dry-run limit buy on the perpetual, priced well under the market so it rests instead of filling, looks like this:
- Webhook:
s=BTC-PERPETUAL b=buy t=limit p=-5% q=1 d=1 - Extension:
e=deribit s=BTC-PERPETUAL b=buy t=limit p=-5% q=1 d=1
The only difference is e=deribit, which tells the browser extension which exchange to route to. On the webhook platform the webhook already knows its exchange, so you leave it out.
Drop the d=1 to send the real order. Trade a size at or above Deribit's minimum for the instrument, and keep the limit price far enough from the market that it won't fill while you test. The cleanest trigger is a single-fire alert on an active instrument; a condition like "price greater than 0" fires it almost instantly.
The example hard-codes a price offset and a quantity, which is what you want for a controlled test. In live use you'll often want a value pulled at fire time. A TradingView alert can write one in: p={{close}} tells TradingView to substitute the candle's close, 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 Deribit orders. You should see the resting limit order in both. Now cancel it:
- Webhook:
s=BTC-PERPETUAL c=order - Extension:
e=deribit s=BTC-PERPETUAL c=order
Order placed, order cancelled, both confirmed in the log and on Deribit. That's the full round trip.
Go live
Connected and tested? Good. A few snags catch people on the first run.
- Invalid credentials. Autoview rejects the key. Almost always a typo on paste, or a key created without trade scope. Re-paste the Access Key and Access Secret, and confirm the permission on Deribit's side.
- Unknown symbol. Deribit names instruments precisely, so
BTC-PERPorBTCUSDwon't resolve. Copy the exact instrument name from Deribit and use that. - Deribit rejects the order. The error in your log comes straight from Deribit, often because the size sat below the instrument'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 versus what you meant. Next you'll want stop-loss and take-profit parameters layered onto these same commands, which is where the automation gets interesting.