Getting started with Gemini on Autoview
By the end of this guide your Gemini 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.
Gemini keeps things simple on Autoview: market and limit orders, over 70 coins. There's no attached stop-loss or take-profit here, so know that going in and size your alerts accordingly.
Step 0: Pick your platform
Autoview comes in two forms, and Gemini 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 Gemini
API credentials are what let Autoview place orders on your account without ever touching your password. You generate them inside Gemini, not inside Autoview, under Settings > API. Gemini keeps its own walkthrough current, so follow theirs for the exact clicks.
When you create the key, two rules are non-negotiable:
- Grant 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.
Gemini calls the two pieces you'll paste into Autoview API Key and API Secret. Copy both somewhere safe before you leave the page. There's no recovering the Secret later. You'd just delete the key and make a new one.
Step 2: Add the credentials to Autoview
Same credentials, slightly different door depending on your platform.
On the extension
Open the extension options, find Gemini in the left menu, and click Add account. Paste in the API Key and API Secret. Leave the key unnamed unless you plan to run more than one Gemini 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 Gemini configuration, and enter the API Key and API 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.
Gemini also has a Sandbox option, wired the same way in Autoview and driven by the same commands as live. Whether you can get a Sandbox account depends on Gemini, so check with Autoview support if you want to test there before touching a real balance.
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.
A note before you send anything: Gemini has no attached stop-loss on Autoview, so trade a size you're comfortable holding, 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 Gemini. 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. Gemini writes its symbols lowercase and joined, like btcusd. A limit buy 5% under the market looks like this:
- Extension:
e=gemini s=btcusd b=buy p=-5% q=1 - Webhook:
s=btcusd b=buy p=-5% q=1
The only difference is e=gemini, 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 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 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 Gemini orders. You should see the resting limit order in both. Now cancel it:
- Extension:
e=gemini s=btcusd c=order - Webhook:
s=btcusd c=order
Order placed, order cancelled, both confirmed in the log and on Gemini. That's the full round trip. Your setup works.
What Gemini doesn't do, so you plan around it
There's no attached stop-loss, no take-profit, and no trailing stop on Gemini through Autoview. Every alert places one order: a market fill or a resting limit. If your strategy needs a protective exit, you're sending it as its own alert and managing it yourself, not attaching it to the entry. Gemini does support a stop-limit trigger on entry, using px= or fpx=, but that's a way to time your entry, not a stop that closes an open position.
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 Gemini's side.
- Account shows disconnected. Nothing executes while it does. Re-check the API Key and API Secret for a stray space.
- Gemini rejects the order. The error in your log comes straight from Gemini, often because the quantity sat below the pair's minimum. Bump the size and resend, or check the pair's minimum on Gemini.
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. From here, build your entry and exit as separate alerts, since Gemini won't bracket them for you. That's where the automation gets interesting.