Binance and Bybit API keys

Creating the key

1. Open API management at the exchange and create a new key dedicated to PipSync. Never reuse one another bot already holds.
2. Permissions: Read plus Spot Trade (for Spot) or Futures Trade (for Futures) on. Withdrawals off. Internal transfer off. PipSync refuses a Bybit key that carries the Withdraw permission.
3. Restrict by IP if the exchange offers it. The PipSync dialog reminds you to IP-restrict the key to the PipSync server IPs, but it does not show the address — ask in the support chat for the current outbound IP address to allowlist.
4. In PipSync: Trading Accounts → Add account → Broker Type Binance (Crypto) or Bybit (Crypto). Enter Account Name, Exchange Mode (Spot or Futures (USDT-M / Linear)), API Key and API Secret. Leave API Endpoint as it is. The exchange shows the secret exactly once.
5. The Testnet box is ticked by default. Untick it for a real account — a live key checked against the exchange's testnet is rejected. Then click Create Account.

If the key is rejected

PipSync checks the key at the exchange before it saves anything. A key the exchange does not accept gives this message: "Credentials could not be verified. Check that the key is correct, has trading permission for the selected market, has NO withdrawal permission, and matches the Testnet setting." Go through that list. If you chose Futures, the key needs futures trading, not just spot. For Bybit, the key is checked against your Unified Trading Account wallet. An IP restriction on the key that does not include PipSync's address makes the check fail with the same message.

"The API key or secret has an invalid format" means a typo or a stray space — keys are 8–512 characters without spaces.

If Binance (Crypto) or Bybit (Crypto) shows as "currently unavailable" in the Broker Type list, the connection service is down. Try again later or message us in the support chat.

Sizing and markets

• Quantities are rounded down to the exchange's step size. A signal below the exchange's minimum quantity or minimum order value is rejected, not rounded up.
• Use Futures (USDT-M / Linear) for signal trading. Every PipSync signal order carries a stop loss and a take profit, and PipSync cannot attach them to a Spot order at the exchange. In Spot mode the order is therefore refused (the error says spot orders do not support attached sl/tp) rather than sent without protection, so signals are not executed on a Spot account.
• In Futures mode PipSync sends the stop loss and take profit to the exchange with the order — on Bybit attached to the order itself, on Binance as separate protective orders placed right after it. If the exchange refuses a protective order, the position can stay open without it and the order is still reported as accepted, so check your open positions and their stops at the exchange.
• Leverage and margin mode stay as you configured them at the exchange. PipSync does not change them.
• Funding fees on perpetuals are charged by the exchange and appear in your exchange statement.
• The key counts as one account against your plan's account limit.

Symbol names

Signals say BTCUSD, BTC/USDT or XBTUSD; the exchange lists BTCUSDT. PipSync translates these spellings automatically (including SOLUSD → SOLUSDT and a trailing .P), so there is nothing to map. The market you trade is the account's Exchange Mode: Spot and Futures are different markets, and a symbol the selected market does not list is refused as an unknown symbol — see “Unknown symbol” — what to change. To keep a channel's signals for an instrument away from the exchange, put it on the channel's Blocked symbols (Channels → your channel → Settings tab → Auto-trade panel → Signal filters).