BullX trading API: none, and trading is suspended

By BLIX · Updated 2026-10-12 · APIs, live data and MCP

API and MCP access come with every BLIX account · sign in with Google · checked October 10, 2026

BullX status

Trading suspended since June 1, 2026; withdrawals open; no relaunch date published

BullX API

None, before or since

BLIX trade API

pump.fun curve and PumpSwap by hand; 2% (1.6% invited); local-sign

Sends

Helius Sender staked path + RPCs, landing reported

Same key

61 data endpoints, AI reads, stream

Community

The BLIX Discord, with your account

Where to take a BullX bot

If you hold funds on BullX, withdraw them first; nothing here touches a BullX account. Facts checked October 10, 2026.

Getting out of BullX

1. Withdraw from BullX while withdrawals are open: SOL and any tokens you still hold go to an address you control. BullX's in-app wallets were never meant to be exported, so send the funds rather than the key.
2. Make a keypair for the bot (or reuse a wallet you already hold the key for) and keep it on the bot's machine. Its public address is the wallet in every BLIX call.
3. Open GET /api/wallet-page/<wallet>: the positions BullX showed are token accounts on the chain, and BLIX reads them from there, with the entry price it can see and the live profit.

Rebuilding the exits

A BullX position carried a take profit and a stop loss. Through the API those are your rule, run against the wallet's live positions; the script sells everything that crosses it and follows each send until the chain confirms it.

# pip install solders requests   (Python 3.10+). Rebuild the exits a BullX position had: a sell, and following it until it lands.
import base64, os, time, requests
from solders.keypair import Keypair
from solders.transaction import Transaction

H = {"authorization": f"Bearer {os.environ['BLIX_KEY']}"}
kp = Keypair.from_base58_string(os.environ["WALLET_SECRET"])
api = lambda m, p, **kw: requests.request(m, f"https://blixvip.com/api/{p}", headers=H, timeout=120, **kw).json()

# what the wallet holds now, from the chain (the positions BullX showed are just token accounts)
me = api("GET", f"wallet-page/{kp.pubkey()}")
for pos in me["positions"]:
    if pos["pnlPct"] < -40 or pos["pnlPct"] > 150:                               # your exit rule
        built = api("POST", "v1/trade/build", json={"wallet": str(kp.pubkey()), "mint": pos["mint"], "side": "sell", "pct": 100})
        if "transaction" not in built: print(pos["symbol"], built["error"]); continue   # e.g. 409 route unsupported
        tx = Transaction.from_bytes(base64.b64decode(built["transaction"]))
        tx.sign([kp], tx.message.recent_blockhash)
        sent = api("POST", "v1/trade/send", json={"transaction": base64.b64encode(bytes(tx)).decode()})
        while sent["status"] == "sent":                                            # follow it until it lands or expires
            time.sleep(1); sent = api("GET", f"v1/trade/{sent['signature']}")
        print(pos["symbol"], sent["status"], sent.get("slot"))

A coin in a pool the hand-built path does not cover answers 409 with "route": "unsupported" rather than a wrong transaction; sell those through the terminal or Jupiter until the routed build ships.

The trade API itself is documented once: the four calls, the flow in curl, what a trade costs, the rules, limits and what is live and what is next.

More on the trade API

More on BullX

BLIX is independent and not affiliated with BullX. Facts about BullX were checked against public sources on October 10, 2026 and can change.

Memecoins are extremely risky and most go to zero. Nothing on this page is financial advice.

Frequently asked questions