Getting started with Gate.io on Autoview
By the end of this guide your Gate.io account is connected to Autoview, your API keys carry the right permissions, and you've fired one real spot order and cancelled it. That last part matters. A dry run tells you your syntax parses. Only a live order tells you the whole chain works.
Two things to settle first: which Autoview you're running, and what your alerts will look like.
Step 0: Pick your platform
Autoview comes in two forms, and Gate.io 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 keys on Gate.io
API keys are the credentials that let Autoview place orders on your account without ever touching your password. You generate them inside Gate.io, not inside Autoview. Gate.io keeps its own walkthrough current, so follow theirs for the exact clicks: Gate.io API documentation.
When you create the key, two rules are non-negotiable:
- Grant trading permission. Autoview needs to place and cancel orders, and read your balances. On Gate.io's permission screen that means enabling spot trading. Without order permission, 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.
Gate.io 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.
Gate.io shows the API Secret once, at creation. Copy both the API Key and the API 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.
Step 2: Add the keys to Autoview
Gate.io gives you two values and Autoview asks for exactly those two. No passphrase, nothing else.
- API Key, the public half.
- API Secret, the private half, the one Gate.io shows once.
Same credentials, slightly different door depending on your platform.
On the extension
Open the extension options, find Gate.io in the left menu, and click Add account. Paste the API Key and API Secret into the matching fields. Leave the key unnamed unless you plan to run more than one Gate.io 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 Gate.io 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.
Step 3: Fire a test order, then cancel it
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: Gate.io commands hit your live account. There's no separate sandbox order here, so trade a size at or above Gate.io's minimum for the pair, and place a limit order far enough from the market that it won't fill while you're testing. A size under the pair's minimum comes back as a notional error.
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 Gate.io. 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. Gate.io spot pairs use the underscore form, so BTC_USDT, not BTCUSDT. A limit buy 5% under the market looks like this:
- Extension:
e=gate s=BTC_USDT b=buy p=-5% q=1 - Webhook:
s=BTC_USDT b=buy p=-5% q=1
The only difference is e=gate, 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 Gate.io orders. You should see the resting limit order in both. Now cancel it:
- Extension:
e=gate s=BTC_USDT c=order - Webhook:
s=BTC_USDT c=order
Order placed, order cancelled, both confirmed in the log and on Gate.io. That's the full round trip. Your setup works.
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 spot trading permission. Re-paste both halves and confirm the permission on Gate.io's side.
- Account shows disconnected. Nothing executes while it does. Re-check the key, and if you whitelisted an IP, confirm the address Autoview is sending from matches the one you approved.
- Gate.io rejects the order. The error in your log comes straight from Gate.io, often because the quantity sat below the pair's minimum. Bump the size and resend, or check the pair on Gate.io. While you're there, confirm you used the underscore pair code.
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. Next you'll want stop-loss, take-profit, and trailing parameters layered onto these same commands. That's where the automation gets interesting.