![]() Please use WebSocket Streams for live updates to avoid bans. Way too much request weight used IP banned until %s. Please use the websocket for live updates to avoid bans. Please use WebSocket Streams for live updates to avoid polling the API. Too much request weight used current limit is %s request weight per %s. Please use the websocket for live updates to avoid polling the API. Too much request weight used current limit is %s request weight per %s %s. Some error messages on error code -1003 have changed: More details on how to upload your RSA public key will be added at a later date.For security reasons, we recommend to use RSA keys instead of HMAC keys when generating an API key.Documentation has been updated to show how to sign a request using an RSA key.POST /sapi/v1/capital/contract/convertible-coins: User can use it to turn on or turn off the BUSD auto-conversion from/to a specific stable coin.GET /sapi/v1/capital/contract/convertible-coins: Get a user's auto-conversion settings in deposit/withdrawal.GET /v1/managed-subaccount/queryTransLogForTradeParent: Trading team can use this api to query managed sub account transfer log.GET /v1/managed-subaccount/queryTransLogForInvestor: Investor can use this api to query managed sub account transfer log.GET /sapi/v1/margin/crossMarginCollateralRatio: Get cross margin collateral ratio.GET /sapi/v1/managed-subaccount/marginAsset: Investor can use this api to query managed sub account margin asset details.GET /sapi/v1/managed-subaccount/fetch-future-asset: Investor can use this api to query managed sub account futures asset details.POST /sapi/v1/sub-account/subAccountApi/ipRestriction/ipList to support master account add IP list for a sub-account API Key.POST /sapi/v1/sub-account/subAccountApi/ipRestriction to support master account enable and disable IP restriction for a sub-account API Key.The following endpoints will be discontinued on Janu6:00 AM UTC:.New fields for executionReport (These fields will only appear if the order has expired due to STP trigger).New fields preventedMatchId and preventedQuantity that can appear in the order query endpoints if the order had expired due to an STP trigger:.makerPreventedQuantity - This will only appear if selfTradePreventionMode set is EXPIRE_MAKER or EXPIRE_BOTH.takerPreventedQuantity - This will only appear if selfTradePreventionMode set is EXPIRE_TAKER or EXPIRE_BOTH.An array preventedMatches with the following fields:.preventedQuantity - Only appears if there was a prevented match.tradeGroupId - This will only appear if account is configured to a tradeGroupId and if there was a prevented match.if an order could have matched with an order of the same account, or the accounts are in the same tradeGroupId): New responses that will appear for all order placement endpoints if there was a prevented match (i.e.New optional parameter selfTradePreventionMode has been added to the following endpoints:.GET /api/v3/myPreventedMatches - This queries the orders that expired due to STP being triggered.New order status: EXPIRED_IN_MATCH - This means that the order expired due to STP being triggered."defaultSelfTradePreventionMode" : "NONE", //If selfTradePreventionMode not provided, this will be the value passed to the engine "allowedSelfTradePreventionModes" : Please refer to GET /api/v3/exchangeInfo from the SPOT API or exchangeInfo from the Websocket API on the status. This will prevent orders from matching with orders from the same account, or accounts under the same tradeGroupId. New Feature: Self-Trade Prevention (aka STP) will be added to the system at a later date. Note that all endpoints are functionally equal, but may vary in performance. ![]() Please refer to GET /api/v3/exchangeInfo from the Rest API or exchangeInfo from the Websocket API on the default and allowed modes.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |