Binance compatibility
Mariex implements a defined USD-M subset. Check the supported behavior before adapting an existing client.
Use the documented subset
The REST paths and many payload shapes follow Binance USD-M conventions. This does not imply support for the full Binance API catalog. Use the generated reference to determine which method and path combinations are available.
Configure your client for https://paper.mariex.com and the routed WebSocket paths in the streaming guide. SDK default hosts, endpoint versions and stream names may need explicit overrides.
| Feature | Supported behavior |
|---|---|
| Markets | BTCUSDT and ETHUSDT perpetuals |
| Collateral | Simulated Paper USDT |
| Order types | LIMIT and MARKET |
| Position mode | One-way, with positionSide BOTH |
| Margin mode | Cross margin |
| Signing | HMAC-SHA256 |
| Account endpoints | Documented /fapi/v2 account, balance and positionRisk paths |
Check order semantics
- LIMIT supports GTC, IOC, FOK and GTX. MARKET must omit price and accepts timeInForce only when absent or IOC.
- Hedge mode, isolated margin, conditional orders, batch operations and order modification are not supported.
- Self-trade prevention defaults to EXPIRE_MAKER. EXPIRE_TAKER and EXPIRE_BOTH are also supported; NONE is rejected for new orders.
- ACK and RESULT return the same synchronous post-match order report.
- Do not send unsupported fields such as closePosition, stopPrice, priceMatch, goodTillDate or workingType in order requests.
Allow for local data behavior
Trades, candles and rolling statistics describe activity on this venue. An empty book or a symbol with no local trades is possible. Mark prices and some market metadata have their own availability rules.
Public market streams use /public or /market prefixes. Only one-minute candles stream over WebSockets. Private events have no replay, so every reconnect requires REST snapshots.
Current account and order state can be visible before the corresponding history records. Integrations must tolerate that delay.
Preserve response types
- Prices, quantities and monetary values commonly use decimal strings. Do not convert them to binary floating-point values for accounting or signing.
- Price, premium-index and 24-hour ticker endpoints return an object when symbol is provided and an array when it is omitted.
- Leverage brackets always return an array. Candle rows are positional tuples with mixed field types.
- The documented v2 account endpoints have no automatic v3 aliases. RSA signing is not supported.