Learning / Exchange Quirks

Exchange Quirks, Notes & Known Limitations

Exchange-specific order behavior, test environments, and limitations of the current Flipr.Cloud integrations. Check the market type covered by each note before using it.

Exchange-Specific Behavior

Smart Syntax is shared across exchanges, but Spot and Futures can support different operations. An exchange API feature is not necessarily implemented in Flipr.Cloud. Use the exchange and market choices available in API Keys for your account.

WEEX Futures: partial TP/SL and independent OCO pairs

Choose the Matching Test Environment

For Bybit, create keys in Demo Trading and select Demo in API Keys. For the other supported environments below, use their own simulated-trading keys and the matching Demo/Testnet setting. Live keys, Testnet keys and Demo keys are not interchangeable. A Testnet toggle alone does not create a simulated account.

Exchange	Test environment	Use in Flipr.Cloud
Binance	Demo	Spot and USD-M Futures use `demo.binance.com` → Settings → API Management.
ByBit	Demo	Bybit → Demo Trading → API Management. Use Demo keys, not Testnet keys.
Bitget	Demo	Create keys in Bitget Demo Trading and enable simulated mode for the selected market.
BloFin	Futures Demo	Futures: `demo-trading.blofin.com` → API Settings. Use the Demo account's credentials.
KuCoin	Legacy sandbox retired	The old sandbox is not a supported testing route in Flipr.Cloud. Keep Testnet Mode disabled. KuCoin notice
Phemex	Testnet	`testnet.phemex.com` → API Keys
BitMEX	Testnet	`testnet.bitmex.com` → API Keys
OKX	Demo	Create a Demo Trading API key in OKX and enable simulated mode in Flipr.Cloud. A live API key does not become a Demo key.
Bitfinex	Paper Trading on exchange	Bitfinex provides paper subaccounts and test symbols on its normal API. Flipr.Cloud's Testnet toggle does not activate this; use Bitfinex's own Paper Trading setup.
Bitunix	Live only in Flipr.Cloud	Spot and Futures integrations use live API endpoints. Keep Testnet Mode disabled.
Kraken Futures	Restricted testing	The public Demo was retired. Kraken's replacement requires onboarding and is not configured in Flipr.Cloud. Kraken testing access
Kraken Spot	Live only in Flipr.Cloud	The Spot integration uses the live API. Keep Testnet Mode disabled.
WEEX	Live only	Mainnet only — keep Testnet Mode disabled
HTX	Live only in Flipr.Cloud	USDT-M Futures use the live API. Keep Testnet Mode disabled.
Toobit	Live only in Flipr.Cloud	The integration uses live API endpoints. Keep Testnet Mode disabled.
MEXC	Live only in Flipr.Cloud	The integration uses live API endpoints. Keep Testnet Mode disabled.

Important Notes

• Demo, Testnet and live API keys belong to different environments; Bybit uses Demo in Flipr.Cloud

• Use simulated mode only for a supported environment above. Some live-only clients keep using live endpoints even if Testnet is selected; WEEX rejects testnet connections.

• Testnet data (balances, positions) resets periodically on some exchanges

• Some features may behave differently on testnet vs mainnet

Contract Sizes

For these linear futures, Smart Syntax quantities are in the base asset. The symbol's quantity step and minimum order value still apply.

Limitations

Minimum order value varies by symbol. Do not assume 5 USDT is enough for every pair. Check the current minimum notional and quantity filters for the instrument; rounding can reduce the submitted amount.
Demo environment: Use Binance Demo Trading credentials for this integration. Demo availability and liquidity can differ from live trading.

Quirks & Notes

Symbol format: Uses ADAUSDT (no separator) for REST API
TP/SL order types: SL uses STOP_MARKET, TP uses TAKE_PROFIT_MARKET
Position mode: Supports both one-way and hedge mode (positionSide: 'BOTH' for one-way)
Price limits: Limit orders must satisfy the instrument's price filters, in Demo and live trading.

Feature Support

Market orders
Limit orders
Stop orders (entry)
TP/SL orders

OCO monitoring
Smart OCO
Cancel all commands
Tags

Paper Trading: Bitfinex provides paper subaccounts with test symbols on its normal API. Flipr.Cloud's Testnet toggle does not activate a paper account; use Bitfinex's own setup for paper trading.
Market selection: Spot and Derivatives use different instruments and account balances. Select the matching market for your API key.
Tags: Flipr.Cloud encodes tags into Bitfinex's numeric client order IDs. The exchange interface may show a number rather than your original tag text.

Contract Sizes

Quantities for the linear futures covered here are expressed in the base asset. Minimum size, quantity step and minimum notional depend on the instrument.

Position TP/SL cancellation is limited in Flipr.Cloud

rem tp, rem sl and rem tpsl can cancel matching separate plan orders, but the current integration does not remove position-attached TP/SL. Manage those protections in Bitget's interface. Closing a position is a trading action, not a substitute for canceling protection.

Bitget's current API documents cancellation of position TP/SL too; that capability is not yet used by Flipr.Cloud. Bitget cancellation API

Limitations

Order minimums: Follow the symbol's minimum quantity and notional. A 5 USDT minimum observed on one pair does not establish the rule for every market.
Two kinds of protection: Position TP/SL and separate plan orders use different API queries. An empty regular-order list does not mean the position has no TP/SL.

Quirks & Notes

Passphrase required: API key + secret + passphrase (3 credentials)
Rounding: Quantities follow the instrument's size step. Some pairs allow fractional units; rounding to a whole coin is not a universal rule.
Symbol format: ADAUSDT → ADA/USDT:USDT → ADAUSDT
productType: Uses USDT-FUTURES for USDT-margined contracts
Position cleanup: Position-attached TP/SL are removed when the position closes. This does not establish one-to-one cancellation between partial exit orders.

Feature Support

Market orders
Limit orders
Stop orders
Position TP/SL and separate plan orders

Cancel all/buy/sell
Remove position-attached TP/SL in Flipr.Cloud
Cancel matching separate plan orders
Tags

Futures quantities: Flipr.Cloud converts the base-asset quantity to contracts using the instrument's contract size. Lot size can change the final amount, especially for partial TP/SL.
Spot quantities: Use base-asset units. The integration handles BitMEX's internal amount representation; do not multiply by an internal precision factor yourself.
Reduce-only: This is a Futures order restriction. BitMEX Spot does not support the same flag.
Testnet: Create a separate Testnet account and API key; live credentials do not select Testnet.

No Stop Orders for Entry

Standalone stop/trigger entries are not supported by this integration. TP/SL fields attached to a normal market or limit order protect its position; they do not make the entry wait for a breakout. Position TP/SL operations require an existing position.

Limitations

No breakout/breakdown entries - Cannot place stop orders without existing position
Misleading errors: "Network Error" when attempting stop order without position

Workarounds

For a breakout entry, send the entry signal from TradingView when the level is reached, or use an exchange integration that supports stop entries. A buy limit above the market (or sell limit below it) can fill immediately; it does not wait for the breakout.

Feature Support

Market orders
Limit orders
Stop orders (entry)
TP/SL on positions

Cancel orders
Position management

No Stop-Loss

Bitunix Spot has no trigger/conditional orders. Stop-loss is not supported. Take-profit works as a limit sell above current price.

Limitations

No SL/TP bracket: Without a stop-loss trigger, OCO cannot provide a protective SL/TP pair. A take-profit can be a pending limit sell.
Order minimums and precision: Follow the selected pair's trading rules. A minimum observed on one pair is not a fixed threshold for every Spot order.

Feature Support

Market orders
Limit orders
Take-profit (limit order)

Stop-loss
Protective SL/TP OCO bracket
Post-only orders
Trigger types (mark/index)
Cancel orders

Contract Sizes

Enter Smart Syntax quantities in the base asset. Flipr.Cloud converts them to contracts using the instrument's contract size and lot step. For example, with 100 ADA per contract, 10 ADA corresponds to 0.1 contracts. Do not pre-convert your input to contracts.

Quirks & Notes

Symbol format: Uses BTC-USDT (hyphen separator)
Passphrase required: API key + secret + passphrase
Broker identification: Handled by the integration; no broker ID is required in Smart Syntax.
Stop order type: Uses orderType: 'trigger'
Price precision: Limit prices and quantities are rounded to the instrument's tick and lot sizes.
API signature: path + method + timestamp + nonce + body (unique order)
Ticker endpoint: /api/v1/market/tickers (plural)

Feature Support

Market orders
Limit orders
Stop orders (trigger)
Stop-limit orders

TP/SL orders
Cancel by tag
Balance query
Scale in/out

Syntax Notes

Use pos for a target position size; it buys or sells the difference from the current position. A target expressed with % uses balance-based sizing; %p refers to the current position. See the Position command guide for supported forms.
Tags stored as {tag}_{hash} in clientOrderId

Contract Sizes

All symbols use 1:1 standard contract size (linear perpetuals)

Unified Trading Account (UTA)

ByBit UTA accounts have account-level margin mode, not per-symbol. CCXT may show marginMode: cross even when account is isolated. Use inline margin isolated syntax to change.

Quirks & Notes

Symbol format: ADAUSDT (no separators) for API
Trigger direction: 1 = above current price, 2 = below current price
Position index: 0 = one-way, 1 = hedge long, 2 = hedge short
Order link ID: Used for client-side tracking and tag matching

Trigger Price Types

Smart Syntax	API Value	Description
`(default)`	LastPrice	Last traded price
`trigger mark`	MarkPrice	Mark price (funding adjusted)
`trigger index`	IndexPrice	Index price (spot average)

Feature Support

Market orders
Limit orders
Stop orders
Stop-limit orders
Post-only orders

TP/SL orders
Mark/Index triggers
Margin mode inline
Hedge mode
Multi-block webhooks

Contract conversion: Enter quantities in the base asset. Flipr.Cloud converts them to contracts and applies the instrument's quantity step; a small partial exit may round below the minimum.
Regular and conditional orders: TP/SL, trigger and trailing orders have separate API lists. Flipr.Cloud combines regular and conditional orders for filtered cancellation.
TP/SL trigger prices: Last and mark are supported for TP/SL; index-triggered TP/SL are rejected rather than silently replaced.

Contract Sizes

These notes cover linear PF_* perpetuals. Quantity increments and minimums depend on the instrument; do not apply these sizing rules to inverse contracts.

The old public Demo is no longer a supported test environment

Kraken has retired its public Futures Demo and now offers testing to qualified clients through onboarding. Flipr.Cloud's Testnet option still targets the old sandbox; it does not switch to the live API or connect to the replacement environment. Kraken testing access

Quirks & Notes

Symbol format: ADAUSD → ADA/USD:USD → PF_ADAUSD
Rounding: Quantities follow the selected instrument's size increment, which may allow fractions.
Credentials: Futures API keys are separate from Kraken Spot API keys.
Tag field: Uses cliOrdId (not orderLinkId)

TP/SL Behavior

Visible in orders API (separate orders with reduceOnly=true)
cancel all includes TP/SL
Native OCO - requires backend monitor

Position and Order Cleanup

A position target and cancellation of pending orders are separate actions. Check remaining orders after closing a position. Standard OCO and Smart OCO use Flipr.Cloud's monitor; they are not atomic exchange-side cancellation.

Feature Support

Market orders
Limit orders
Stop orders
Stop-limit orders

TP/SL orders
sl-or-tp combined
OCO monitoring
Smart OCO

Known Requirements

Three API credentials: API key, API secret and API passphrase. The passphrase is set when creating the API key; the account's trading password is a different credential and is not entered in Flipr.Cloud. KuCoin authentication
Futures quantities: Enter the base-asset quantity. Flipr.Cloud converts it to the instrument's contracts; contract size and lot steps can limit small partial exits.
Testing: The retired sandbox is not a supported Demo route in Flipr.Cloud. Keep Testnet Mode disabled; a demo product in KuCoin's interface does not establish API compatibility.

Choose the supported market: Spot access does not imply Futures access. Use the market choices enabled in API Keys; do not reuse a Futures setup for a Spot key.
Spot positions: Spot orders trade the asset balance. Futures concepts such as opening a short or setting leverage do not apply to this Spot integration.
Testnet setting: The current integration keeps live API endpoints even if the legacy testnet flag is set. Keep simulated mode disabled.

Credentials: API key, secret and passphrase. Create a separate Demo Trading API key for simulated mode.
Futures quantities: Smart Syntax uses the base asset. Flipr.Cloud converts it to contracts using the instrument's contract value and lot step; very small quantities can be below the minimum.
Conditional orders: TP/SL and trigger orders have a separate algo-order list. Check that list as well as ordinary pending orders when verifying protections.
Margin mode: Set cross or isolated explicitly when the strategy depends on it. Account and instrument settings affect which combinations OKX accepts.

Full and partial protection: Flipr.Cloud uses separate exit orders for partial TP/SL quantities instead of relying on full-position attached TP/SL.
Existing positions: Phemex can reject attaching TP/SL to an entry when a position already exists. The integration then submits the entry without those attachments and handles protection separately. Verify the entry and each protection independently.
Testnet: Create the API key in the Phemex Testnet account and select simulated mode in Flipr.Cloud. Phemex API environments

Position TP/SL and tags need separate handling

Native position TP/SL are different from standalone conditional orders. Their visibility and cancellation are limited in the current Flipr.Cloud integration.

Limitations

rem tp, rem sl, rem tpsl do not remove native position TP/SL in this integration. Manage those protections in Toobit's interface. Separate conditional orders use a different query and cancellation path.
rem #tag is not reliable across all order types: some order paths do not preserve the tag. Prefer the exchange order ID for an individual cancellation and verify the remaining orders.

Working Commands

rem all, rem buy, rem sell for supported open-order lists
Market and limit orders
TP/SL placement, subject to the position-protection limitation above

Native TP/SL are attached to the position and are removed when that position closes. Closing the position and canceling a particular protection are different trading decisions.

Partial TP/SL: pair each exit with Flipr.Cloud OCO

Read before using partial exits on WEEX

WEEX does not provide native OCO for partial TP/SL, even when those orders are attached to the position. If a TP closes only part of the position, its matching SL can remain open; the same applies to a TP after a partial SL exit. Use Flipr.Cloud OCO when each partial exit must cancel its opposite protection.

WEEX automatically removes the remaining position TP/SL when the entire position on that side closes. This does not pair exits while a position remains open. WEEX TP/SL documentation

Four take profits, two stop-loss levels

Start with a 40 ADA long position. Each of four take profits closes 25% (10 ADA). To cover 50% at each of two stop-loss levels, split each level into two SL orders of 25% at the same price. You now have four equal-size SL/TP pairs: eight orders in total, with one tag and one OCO group per pair.

Pair tag	Each order	SL price	TP price
`#p1`	10 ADA (25%)	0.196	0.204
`#p2`	10 ADA (25%)	0.196	0.208
`#p3`	10 ADA (25%)	0.192	0.212
`#p4`	10 ADA (25%)	0.192	0.216

These are illustrative prices for an entry around 0.200 USDT, not current market prices. Adapt the quantity and levels to the market and its order minimums. Replace WEEX_F with your saved bot label. The example starts with no existing position or orders on this symbol and assumes all 40 ADA remain open while the protections are placed, so each 25%p is 10 ADA.

ADAUSDT on WEEX_F
market long 40
stoploss long 25%p at .196 #p1
takeprofit long 25%p at .204 #p1
stoploss long 25%p at .196 #p2
takeprofit long 25%p at .208 #p2
stoploss long 25%p at .192 #p3
takeprofit long 25%p at .212 #p3
stoploss long 25%p at .192 #p4
takeprofit long 25%p at .216 #p4
oco #p1
oco #p2
oco #p3
oco #p4

Each SL and its matching TP share a tag. The corresponding oco #tag command activates their OCO group; adding a tag alone does not activate OCO. Multiple price levels require separate stoploss and takeprofit commands as shown. An entry supports one inline SL and one inline TP; repeating either inline replaces the earlier level instead of adding another.

Only the matching protection is canceled

If TP #p1 fills all its 10 ADA, Flipr.Cloud cancels SL #p1. The other three pairs remain active for the remaining 30 ADA.
If an SL fills instead, Flipr.Cloud cancels the TP with the same tag. Both SL orders at the same price can execute: each cancels its own TP.
Manually canceling either order also activates standard OCO and cancels its partner.

Use one standard OCO group per pair

Keep the four oco #tag commands. Replacing them with one oco session would group all eight exits: the first completed exit would cancel the other orders in that group. Likewise, putting a 50% SL and two 25% TPs in one group would cancel both remaining orders when the first TP fills.

smart-oco watches for the position to close or change side. It lets partial exits proceed without canceling their partners, so it does not provide the pair-by-pair behavior shown here.

What the pairing does and does not cover

Use fresh, distinct tags for every concurrently active set on the same account and symbol. Avoid overlapping names such as #p1 and #p1_extra: the shorter tag also selects orders with that suffix.
A partial exit from the position is different from a partial fill of one order. If only 5 of a 10 ADA order fills and that order stays open, the matching order stays at 10 ADA. OCO does not resize it; cancellation follows a confirmed full fill or cancellation of its partner.
Flipr.Cloud's monitor sends cancellations asynchronously. The two orders remain separate exchange orders, so cancellation is not atomic and depends on the monitor and exchange connection being available. Tags group orders; they do not reserve separate positions.

Verified on WEEX Futures on 24 October 2026: two 10 ADA SL exits reduced a long position from 40 to 20 ADA, and a subsequent 10 ADA TP reduced it to 10 ADA. Flipr.Cloud canceled only each completed exit's partner; the final pair remained intact.

An executed entry does not guarantee TP/SL protection

Attached TP/SL orders are supported. However, a market entry can execute even if an attached TP or SL fails to be created. WEEX confirmed that this can happen when the trigger price has already been crossed by the time the entry executes.

Recommendations

After the entry fills, verify each requested TP and SL in WEEX's current conditional orders. If an order is absent, also check its history and fills: it may already have triggered.
Allow for price movement between submission and execution when choosing trigger levels, within your risk limits. A greater distance does not guarantee acceptance.
If Flipr.Cloud reports an executed entry with unconfirmed protection, check the existing position and its TP/SL before taking further action. Do not repeat the executed entry.

Confirmed by WEEX support on 26 October 2026. WEEX conditional order documentation

Content reviewed: 5 November 2026

These notes describe the current Flipr.Cloud integrations. Exchange requirements and instrument limits can change; live examples retain their own verification dates. If behavior differs from these notes, report it to support with the exchange, market type and execution details.

Exchange Quirks, Notes & Known Limitations

Demo and Testnet Support

Binance

Bitfinex

Bitget

BitMEX

Bitunix Futures

Bitunix Spot

BloFin

ByBit

HTX

Kraken Futures

KuCoin

MEXC

OKX

Phemex

Toobit

WEEX Futures

Partial TP/SL: pair each exit with Flipr.Cloud OCO

Four take profits, two stop-loss levels

Only the matching protection is canceled

What the pairing does and does not cover

Learning