> For the complete documentation index, see [llms.txt](https://support.tiger.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.tiger.com/english/connections/crypto-exchanges/binance-via-tiger.com-broker.md).
# Binance via Tiger.com Broker
Tiger.com Broker allows you to reduce trading commissions on the Binance exchange by up to 35%, as well as use the Tiger.com Windows cryptocurrency license for free without any limitations.
Via Tiger.com Broker, you can connect two Binance account types:
| Account type | What it is |
| ------------ | ------------------------------------- |
| **Futures** | USDⓈ-M futures (settled in USDT/USDC) |
| **Spot** | Spot trading |
Below: how to get API keys in Tiger.com Broker, how to add the connection in the terminal, and how the Spot and Futures settings differ.
## Step 1. API keys in Tiger.com Broker
1. Register on the [Tiger.com Broker website](https://broker.tiger.com/) (if you haven't registered yet) and log into your account.
2. Create API keys in the Tiger.com Broker personal area by completing the necessary settings, and save the public and private keys in a secure place - they will be required for further connection.
3. Pass through the KYC verification and connect two-factor authentication to enhance the security of the account and the safety of funds.
{% hint style="info" %}
Tiger.com Broker keys are **HMAC** only. Ed25519 keys are not used for this connection.
{% endhint %}
## Step 2. Connecting in the terminal
1. Launch the Tiger.com Windows terminal and in the main menu select **File → Connections → Configure**.
2. Click **+ New connection** and select **Binance via Tiger.com Broker** on the **Crypto exchanges** tab:
Create new connection
3. Select the account type and enter the public and private keys you got in Step 1.
4. Click **Connect to Tiger.com Broker**.
### General
These settings are available for both account types:
| Field | Description |
| ------------------------ | ----------------------------------------------------------------------------------------------------- |
| **Connection name** | Editable. Useful if you have several connections, e.g. “Broker Spot” and “Broker Futures”. |
| **Account type** | Spot or Futures. See [Settings by account type](#settings-by-account-type) for the specifics of each. |
| **View-only mode** | Quotes, order book and tape without trading. API keys are not needed in this mode. |
| **API Key / API Secret** | The public and private keys from your Tiger.com Broker personal area. Hidden in view-only mode. |
| **Proxy** | Select a proxy from the list or add a new one for the connection. See [Proxy](#proxy). |
| **Order book depth** | How many order book levels to load; 3000 by default. |
### Settings by account type
{% tabs %}
{% tab title="Futures" %}
USDⓈ-M futures via Tiger.com Broker — contracts settled in USDT or USDC.
Two options are available in addition to the common fields.
**Websocket API for orders**
Disabled by default. Places and cancels futures orders via the Binance WebSocket API (when the option is disabled — via the REST API). The only way to find out which connection suits you best is to experiment: try trading with the option enabled and disabled.
**Order book and tape synchronization**
Aligns the trade tape with the spread in the Binance Futures order book.
Why it's needed: since 23.04.2026, Binance delivers the order book and the tape over two separate connections. Their subscription times may differ slightly, so the tape may drift from the spread. The exchange plans to fix this, but there is no timeline yet.
{% hint style="warning" %}
This option is experimental and may cause order books to work unstably. If the order book freezes or market data stops during volatility, disable it.
{% endhint %}
{% endtab %}
{% tab title="Spot" %}
Spot trading on Binance via Tiger.com Broker.
Server and port selection are available for Spot only — they help if the connection is unstable or fails to establish. Try different servers/ports to find the one that works best for you.
**Server selection** — the address the terminal uses to work with the exchange:
* `https://api.binance.com` — the main server, selected by default;
* `https://api-gcp.binance.com` — an alternative server;
* `https://api1.binance.com` … `https://api4.binance.com` — additional servers.
**Connection port** — `9443` (default) or `443`.
{% hint style="info" %}
If you have trouble connecting to Spot, try other servers one by one and port `443`.
{% endhint %}
{% endtab %}
{% endtabs %}
### Proxy
If a proxy is selected, you can choose which data goes through it:
| Option | What goes through the proxy |
| ----------------------------- | -------------------------------------------------------------- |
| **Use proxy for market data** | Market data for the instrument: quotes, order book, trade tape |
| **Use proxy for user data** | Your account information: balances, positions, orders |
| **Use proxy for orders** | Placing and cancelling orders |
All three are checked by default. For example, you can keep market data on a direct connection and send only orders and account data through the proxy. Proxies are added in the [Connections](/english/connections.md) window.
{% hint style="info" %}
Unchecking the boxes doesn't turn the proxy off completely. To connect without a proxy, select the no-proxy option in the **Proxy** field.
{% endhint %}
## FAQ: connection problems
Spot won't connect or the connection keeps dropping
1. Open the connection settings and change the **port** to `443`.
2. If that doesn't help, try other servers one by one in **Server selection**: `api-gcp`, `api1`–`api4`.
3. Check whether your ISP blocks Binance.
Learn more about stabilizing your connection in our article [How to Improve Connection Stability to the Exchange?](/english/frequently-asked-questions/how-to-improve-connection-stability-to-the-exchange.md)
The trade tape drifts from the spread in the Futures order book
The mismatch between the trade tape and the order book spread is caused by Binance's switch to new APIs (23.04.2026). Previously, the order book and the tape came through a single websocket, so the data was consistent. Now they are two separate connections, and their subscription times may differ slightly — this causes the desynchronization. The exchange plans to fix this, but there are no timelines or official solutions yet.
On our side, we've added the "Order book and tape synchronization" option to the Binance/TigerX connector settings. It minimizes the mismatch between the trade tape and the spread in the Binance Futures order book. With the frequency set to 100 ms, the official Binance depth\@100ms channel is used. With the "maximum" frequency, the depth\@0ms channel is used; it is unofficial (although the exchange also streams data through it), so it may be less stable.
Please note that the option is experimental, so enabling it may cause order books to work unstably. If you notice order books freezing and market data stopping during volatility, disable it.
The order book freezes or market data stops during volatility
If **Order book and tape synchronization** is enabled, disable it — the option is experimental and may cause these symptoms.
If it's disabled, go through the basic recommendations in [How to Improve Connection Stability to the Exchange?](/english/frequently-asked-questions/how-to-improve-connection-stability-to-the-exchange.md)
Key or signature error when connecting
Check that:
* the keys were created in your **Tiger.com Broker** personal area specifically for Binance;
* the keys are copied in full, without spaces;
* the correct **Account type** is selected;
* the instrument selected in the order book/chart matches the connection type.
Endless connecting, frequent disconnections
Reconnections, dropped connections and no connection are most often caused by network settings, local restrictions or blocking. The Tiger.com terminal does not affect the quality of your connection to the exchange — you connect directly to the exchange's servers.
Learn more about stabilizing your connection in our article [How to Improve Connection Stability to the Exchange?](/english/frequently-asked-questions/how-to-improve-connection-stability-to-the-exchange.md)
High ping
The order book (DOM indicators) shows two values:\
**The first line** is the ping of the last action, e.g. placing or cancelling an order.
**The second line** is the delay in receiving order book data from the exchange. It is calculated as the difference between the time the exchange sent the market data and the time the terminal received it.
High values may depend on the load on the exchange's servers and activity in the instrument. The second line may also be affected by time synchronization on your PC, so if needed, try syncing the time in Windows time settings and then restart the terminal.
Learn more about stabilizing your connection in our article [How to Improve Connection Stability to the Exchange?](/english/frequently-asked-questions/how-to-improve-connection-stability-to-the-exchange.md)
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://support.tiger.com/english/connections/crypto-exchanges/binance-via-tiger.com-broker.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
