Getting started with HTX on Autoview
By the end of this guide your HTX 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.
HTX is the exchange formerly known as Huobi. Autoview's connector answers to either name, so e=htx and e=huobi both route the same place.
Step 0: Pick your platform
Autoview comes in two forms, and HTX 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 HTX
API credentials are what let Autoview place orders on your account without ever touching your password. You generate them inside HTX, not inside Autoview, under API Management. HTX keeps its own walkthrough current, so follow theirs for the exact clicks. There's no demo account here, so this key connects straight to your live balance.
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.
HTX calls the two pieces you'll paste into Autoview Access Key and Secret Key. Copy both somewhere safe before you leave the page. There's no recovering the Secret Key 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 HTX in the left menu, and click Add account. Paste in the Access Key and Secret Key. Leave the key unnamed unless you plan to run more than one HTX 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 HTX configuration, and enter the Access Key and Secret Key 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 why a live signal did nothing. Don't skip it. Because there's no demo account here, keep this one deliberately small: trade a size at or above HTX's minimum for the pair, 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 HTX. 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. HTX writes its symbols lowercase and joined, like btcusdt. A limit buy 5% under the market looks like this:
- Extension:
e=htx s=btcusdt b=buy p=-5% q=1 - Webhook:
s=btcusdt b=buy p=-5% q=1
The only difference is e=htx, 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 HTX orders. You should see the resting limit order in both. Now cancel it:
- Extension:
e=htx s=btcusdt c=order - Webhook:
s=btcusdt c=order
Order placed, order cancelled, both confirmed in the log and on HTX. That's the full round trip. Your setup works.
One HTX quirk worth knowing before you build a real strategy
HTX doesn't attach a stop-loss or take-profit to your entry order. Instead, a protective exit is its own standalone trigger order, placed with px= at the price you want it to fire. If you want a trailing stop, HTX requires that trigger price alongside it; send ts= without px= or fpx= and Autoview stops you before it sends anything, rather than guessing what you meant. Plan on sending your entry and your protective trigger as two separate alerts, not one combined command.
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 HTX's side.
- Account shows disconnected. Nothing executes while it does. Re-check the Access Key and Secret Key for a stray space.
- HTX rejects the order. The error in your log comes straight from HTX, often because the quantity sat below the pair's minimum. Bump the size and resend, or check the pair's minimum on HTX.
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 a trigger order layered on as its own alert for your stop-loss or take-profit. That's where the automation gets interesting.