All Help Center topics

HELP CENTER · STEP-BY-STEP GUIDE

Connect QATS to your tools

The Chrome extension, Bybit, your own bots and TradingView: how to set up each one, with screenshots of where to click.

One account per key Same rules as the terminal No key can withdraw
BEFORE YOU BEGIN

Every connection trades one QATS account through the same rules and risk checks as the terminal. None of them can request a payout, see billing or reach another account. Revoking a connection stops it at once; it does not close positions or cancel orders.

Choose a connection

Open Profile & settings → External connections. Three blocks say what you can do; each shows whether something in it is already set up. A block with more than one way opens its choice; Trade on Bybit has one way and opens its setup at once. The buttons above every page take you back a level.

ON THIS SCREENFind the highlighted controls Click to enlarge
What to look for

Select a numbered step to zoom straight to that control.

QATS screen captured on a test account. Your accounts, names and dates will differ.
ON THIS SCREENFind the highlighted controls Click to enlarge
What to look for

Select a numbered step to zoom straight to that control.

QATS screen captured on a test account. Your accounts, names and dates will differ.
You want toUse
Click Buy or Sell on a TradingView chartQATS Trade for Chrome
Let alerts or a Pine strategy trade for youTradingView
Trade the challenge in Bybit’s own app or terminalBybit
Run your own codeTrading API, tested first on the sandbox

Install QATS Trade

Open External connections → Trade from charts → QATS Trade for Chrome on a computer. It works in Chrome 130 or later, Edge and Brave.

ON THIS SCREENFind the highlighted controls Click to enlarge
What to look for

Select a numbered step to zoom straight to that control.

QATS screen captured on a test account. Your accounts, names and dates will differ.
  1. Press Download QATS Trade: Chrome saves a file such as qats-trade-chrome-1.8.0.zip. No need to unzip it.
  2. Open chrome://extensions in a new tab (the panel copies the address) and turn on Developer mode at the top right.
  3. Drag the downloaded file onto that page and release it on Drop to install: Chrome installs QATS Trade by itself. Nothing happens? Unzip it, press Load unpacked and choose the folder.
  4. A QATS Trade older than 1.6 in the list? Press Remove on it: it cannot connect with QATS.
  5. Go back to the QATS tab. The page finds QATS Trade and opens the QATS window to connect it: see the next step. Every step with screenshots.
ON THIS SCREENFind the highlighted controls Click to enlarge
What to look for

Select a numbered step to zoom straight to that control.

Chrome’s Extensions page with English labels, captured with an earlier version. In another language the buttons are in the same places.
Chrome runs extensions installed outside the Chrome Web Store only in Developer mode, and may remind you of that at start; QATS Trade keeps working. Installed from the Chrome Web Store, it needs neither Developer mode nor the folder.

Connect with QATS

Right after the install a small QATS window opens by itself; later, press Connect with QATS on this page, in the ticket or in the extension’s settings. Sign in if asked, choose the accounts QATS Trade may trade and press Approve. The window closes and the ticket is ready. No key is created, shown, copied or pasted: QATS gives the extension its own access, which works only for the accounts you approved.

The window says exactly what QATS Trade can do: see the balance, positions, orders and loss limits of those accounts, and place, change and close orders on them with the same rules and risk checks as the terminal. It cannot request payouts, see billing or personal details, create keys or reach any other account. An account traded on your own Bybit is connected read-only.

The QATS window shows a short code, such as K7-3QX, and QATS Trade shows the same code where you pressed Connect. Tick the accounts only when the codes match; a different code, or a window you did not open, means press Deny. Approving needs a sign-in from the last 12 hours, and QATS emails you about every new connection. Changing your password or signing out everywhere disconnects QATS Trade too.

ON THIS SCREENFind the highlighted controls Click to enlarge
What to look for

Select a numbered step to zoom straight to that control.

QATS screen captured on a test account. Your accounts, names and dates will differ.
ON THIS SCREENFind the highlighted controls Click to enlarge
What to look for

Select a numbered step to zoom straight to that control.

QATS screen captured on a test account. Your accounts, names and dates will differ.
  1. More than one account: choose them all in the QATS window, or press Change accounts later. The account name on the ticket becomes a switch.
  2. The connection renews itself while you use it. Unused for 30 days, or after 180 days, the ticket shows Connect with QATS again: one click and Approve.
  3. Each browser you connected is listed on this page under Connected browsers, with its accounts and when it was last used. Revoke there, or Disconnect in the extension’s settings, cuts its access at once; positions and orders stay as they are.

Trade from the chart

On any TradingView chart the ticket opens top right and follows the chart’s symbol: Buy / Long, Sell / Short, market, limit and stop entries, size in coins, dollars or risk at the stop, with take profit and stop loss. Your position, its stop and target and your orders are drawn on the chart; drag a line to move it. Under the account line the ticket shows what is left before your daily loss limit and maximum loss.

On Binance, Bybit, Coinglass or any other chart site, press the QATS Trade toolbar button and choose Show the panel here.

Every ticket control explained

Use an API key instead

Prefer keys, or still on a QATS Trade older than 1.6? Open Advanced: use an API key instead under the steps, press Create a key for QATS Trade and copy the key from the dialog. Then press the QATS Trade toolbar button → Settings → Advanced: use an API key instead, paste it and press Save and test. A key made in QATS lasts 30 days and is revoked under Bots and API → Your keys.

To update QATS Trade, download it again and drag the new file onto chrome://extensions: it replaces the installed one. Your connected accounts stay.

Move a challenge to your Bybit demo account

A crypto challenge that has not traded yet can be traded on your own Bybit Demo Trading account instead of the QATS terminal. QATS reads that account with a read-only key and applies the challenge rules to it.

ON THIS SCREENFind the highlighted controls Click to enlarge
What to look for

Select a numbered step to zoom straight to that control.

QATS screen captured on a test account. Your accounts, names and dates will differ.
  1. On Bybit switch to Demo Trading . Set USDC, BTC and ETH to zero and the USDT balance to your challenge size. Close every position.
  2. While still in Demo Trading, create an API key : Read-Only, with Orders and Positions ticked. A key that can transfer or withdraw is refused.
  3. In QATS open External connections → Trade on Bybit, choose the challenge, paste the key and the secret and press Connect Bybit. QATS checks the key with Bybit first and moves the challenge only if every check passes.

What changes after you connect Bybit

RuleWhat it means
The challenge stays on BybitTrading in the QATS terminal is closed for it; Trade shows its Bybit state.
Starting equity is fixedIt is read when you connect. A deposit, withdrawal or transfer on that Bybit account freezes the challenge for review.
Only USDT perpetuals countSpot and USDC contracts are not part of the challenge.
Your own terminalGive it its own Demo Trading key with trading rights: Bybit’s app, Tealstreet, Tiger.Trade 23.2+ or ccxt/Freqtrade with demo trading on. QATS keeps its read-only key.
TradingView’s Bybit panel, ATAS, Quantower and CScalp cannot trade a Bybit Demo account. To trade from TradingView, keep the challenge on QATS and use QATS Trade or TradingView alerts.

Create an API key for a bot

Open External connections → Bots and API → Trading API and press Create API key. One key belongs to one account; give each bot its own key so you can revoke one without stopping the rest.

ON THIS SCREENFind the highlighted controls Click to enlarge
What to look for

Select a numbered step to zoom straight to that control.

QATS screen captured on a test account. Your accounts, names and dates will differ.
  1. Check the account, name the key, choose the permission and press Continue, then Create API key.
  2. Copy the key from the last screen into your bot’s secret store. It is shown once; QATS keeps only a hash of it.
  3. Send it as a Bearer header over HTTPS and your own Idempotency-Key on every write, so a retry cannot place a second order.
First requestReads the account the key belongs to.
curl -H "Authorization: Bearer qats_trade_…" \
  https://prop.qats.us/api/v1/trading/account

Your keys, expiry and revoking

ON THIS SCREENFind the highlighted controls Click to enlarge
What to look for

Select a numbered step to zoom straight to that control.

QATS screen captured on a test account. Your accounts, names and dates will differ.

Keys last 30 days. To replace one, create the new key, update your bot, check a read, then revoke the old key. Revoked and expired keys are kept in the folded list under the table.

Test on the free sandbox

Open Sandbox account in the account switcher, then Keys & connections. Choose Trading API for a bot or script, or TradingView alerts for Pine strategies and chart signals. Both use the same separate $100,000 virtual account. If you have not created one yet, choose the market and price venue and press Create free sandbox. Nothing there counts towards a challenge.

ON THIS SCREENFind the highlighted controls Click to enlarge
What to look for

Select a numbered step to zoom straight to that control.

Actual local QATS screen with a virtual QA account and no displayed secret. On the public site use https://prop.qats.us/api/sandbox/v1; your sandbox account, balance and keys will differ.
Open sandbox connections
Check the current account and price venue before connecting. Follow requests, working orders and confirmed fills in Bot activity. A reset under Start over with a fresh sandbox retires the test account, cancels its orders and revokes its keys and webhooks. Create new ones afterwards.

Trade from TradingView alerts

Open External connections → Trade from charts → TradingView alerts and press Create webhook. You get your personal webhook URL, which carries the key: paste it under Notifications → Webhook URL of a TradingView alert. With the QATS Ticket indicator that is the only thing you paste; an alert of your own also takes a ready message under Message. A Pine strategy alert keeps QATS in the strategy’s position; a chart alert buys, sells or closes.

ON THIS SCREENFind the highlighted controls Click to enlarge
What to look for

Select a numbered step to zoom straight to that control.

QATS screen captured on a test account. Your accounts, names and dates will differ.
The full TradingView guide

Something does not work

What you seeWhat to do
The page keeps saying Waiting for QATS TradeIn chrome://extensions check that QATS Trade is switched on and shows 1.6.0 or later; an older one cannot connect with QATS, remove it and drop the new file. Then reload the QATS page. In another browser profile, press Connect with QATS in the extension’s settings.
QATS Trade did not answer or the QATS window closedReload the QATS page and press Connect with QATS again. Nothing is connected until you press Approve.
Connect is not offeredYou need an account that trades in the QATS terminal. A challenge on Bybit is traded on Bybit.
Buy and Sell are grey: The chart shows … not …The chart shows another market than the ticket trades. Switch the chart to the QATS instrument, or pick the instrument in the ticket.
The ticket says Chart lines are off or The price check is offTradingView changed its page and QATS Trade turned that part off; trading works as usual. The extension’s settings show what works under Chart link. Update QATS Trade when a new version is out.
The ticket shows Connect with QATS againThe connection was revoked, or not used for 30 days. Press Connect with QATS and Approve. A pasted key that expired is replaced in the extension’s settings.
QATS no longer accepts this connection for this accountThe connection was revoked in QATS (Connected browsers → Revoke, a password or email change, or sign out everywhere), it expired, or the account closed. Press Connect with QATS and Approve again.
QATS does not accept this API key (revoked, expired or mistyped)The key you pasted in the extension’s settings no longer works: keys made in QATS last 30 days. Create a new key under Bots and API → Trading API, or switch to Connect with QATS, which needs no key.
An order says Not sent: …QATS refused it and nothing was placed; the sentence says why. For the price checks, leverage and slippage messages, see order refusals explained.
Bybit refuses the keyThe message says which check failed: not Demo Trading, not read-only, open positions, or a balance other than USDT at the challenge size. Fix it on Bybit and connect again.
Your bot gets 401 or 403The key expired, was revoked, is read-only, or the request came from an address outside its list. Check it under Bots and API → Trading API → Your keys.
READY?

Open External connections

Choose a card and follow its steps.

Open connections
More guidesExplore every QATS topic in one place.
Open Help Center
Screenshots come from a QATS test account. Bybit and TradingView screens can change.