Features Sentinel Brokers Community Pricing About Us Why VEXA Support Get Access Now

Connect Tiger Brokers

Tiger's sync is live but its setup is the most technical of any broker: an RSA key pair, in PKCS#1 format only, plus your Tiger ID and App Key.

Same on every platform Updated

What this does

Tiger Brokers syncs automatically once connected, pulling once a day. Getting connected takes more work than any other broker in VEXA, so read this before you start rather than halfway through.

Before you start

  • Approval takes a day or two. Tiger reviews your developer application before issuing the App Key.
  • The private key must be in PKCS#1 format. It begins -----BEGIN RSA PRIVATE KEY-----. A PKCS#8 key begins -----BEGIN PRIVATE KEY----- and VEXA cannot use it. This one detail causes more Tiger tickets than everything else combined.
  • Set your broker server timezone, matched to the region you trade. See Set your broker server timezone.
  • Three years of history, at 60 requests a minute.
  • Global futures are handled on Chicago time.

Set up the automatic sync

Same on every platform

  1. Sign in at open.tigerbrokers.com and open the Console.
  2. Go to App Management and create a new app.
  3. Generate an RSA key pair with Tiger’s tool. Upload the public key to Tiger and keep the private key.
  4. Confirm the private key is PKCS#1. If the first line does not read -----BEGIN RSA PRIVATE KEY-----, convert it before continuing.
  5. Wait for approval, then collect your App Key. It is not the same thing as the private key.
  6. In VEXA, open the Tiger Brokers page and enter your Tiger ID, which is the numeric account id, your App Key, and paste the whole multi-line private key.
  7. Choose your trading region: US, Hong Kong, Singapore or Australia. This decides which markets sync.
  8. Save the connection.

Steps

Same on every platform

Export a file instead, or as a backfill

  1. Open the Tiger Trade app.
  2. Go to Account, then History, then trade history.
  3. Set the date range.
  4. Export the file.
  5. Upload it to VEXA.

Limits and gotchas

  • The region setting is not cosmetic. Pick the wrong one and trades from the markets you actually trade never arrive.
  • Paste the private key whole, including the header and footer lines and the line breaks. A key pasted as a single line is rejected.
  • Three years is the API ceiling. For older history, upload a file.

What you should see

After saving, the account shows an Active badge and a first pull runs. From then on it syncs once a day.

After a file upload, a result panel naming the Tiger trade history format.

If it doesn’t work

  • The credentials were rejected. Check the private key format first. PKCS#8 is the usual cause.
  • It connects but nothing arrives. The region is wrong for the markets you trade.
  • Trades land on the wrong day. The broker server timezone does not match the market. Fix it and re-import.

Related

Connect a broker Where the broker picker lives on each device, how to name the account, and what a successful first connection looks like. The three timezones VEXA holds The three different timezones VEXA holds, which brokers need the server one set, and where the setting lives on each device. When VEXA syncs your trades automatically How often each connected broker is pulled, why there is no auto-sync indicator anywhere in the app, and how to tell whether yours is running.

Still stuck? Email support@vexatrade.ai.