How to specify a trading area for fcoin spot
Author: fangzaixiang, Created: 2019-11-20 17:18:51, Updated:I looked at the interface of fcoin.
If you want to know how to specify a trading zone, we can use the fmz side of exchange.Buy.
- Please teach me about the _C function.
- Is the K-line of GetRecords returning data by default only 20 bits?
- Access to historical data
- Choi Wei asks about the earnings of FMZ's reassessment
- I hope to provide a general protocol plugin for a FEX exchange, newbies can't do that, thank you.
- Is it possible to automatically switch cryptocurrency futures trading? For example, the OKEX exchange switches from BTC_USD to ETH_USD
- In this case, the code is always {"code":-1121, "msg:"Invalid symbol. "}
- Is it better to hang one pair or multiple pairs?
- Binance, the same code, the host in Hong Kong can run Linux instead of Windows in Singapore
- Binance error Futures_OP 4: 429: {"code":-1003, "msg":"Too much request weight used; current limit is 1200 request weight per 1 MINUTE.
- bybit futures exchange aggregate
- Fcoin exchange robot listing order buy successfully shows to get order information failed, ID:, please point
- Ok, the batch ordering example is wrong.
- Fcoin exchange connects to API error report account failed to access, ask for God's point
- Can a contract hold two positions at the same time?
- Please, how about getting the red-green columns in MACD and the empty red-green columns in MACD?
- How does the FMZ platform enable robots to automatically monitor error reports and, if there is a mistake, strategize through API extensions?
- Exchange.IO uses the example in the manual to report errors
- How to limit the price of a small number of digits when the disk is running
- How should the RSI monitoring code be written?
The Little DreamThis interface can be accessed directly using exchange.IO, specifying this parameter.
The Little DreamI'm not being polite.
fangzaixiangOkay, fine, thank you.
The Little DreamAs described in the API documentation for exchange.IO exchange.IO (("api", "POST", "/v2/orders", "xxxx") The fourth parameter is in the form a=1&b=2 and so on. Signatures such as time are all wrapped up and can only be used with input parameters.
The Little DreamAs described in the API documentation for exchange.IO exchange.IO (("api", "POST", "/v2/orders", "xxxx") The fourth parameter is of the form a=1&b=2 and so on.
fangzaixiangAt the beginning it was not timed, and it was not working, but after looking at the interface of fcoin it looked like it said to add time to the front https://developer.fcoin.com/zh.html?javascript#05e32f581f The code is: The following are the prepared data of the signatories: POSThttps://api.fcoin.com/v2/orders1523069544359amount=100.0&price=100.0&side=buy&symbol=btcusdt&type=limit Now I'm going back to the original code: var buyOrders = "symbol="+ExchangeCurr+" & side=buy&type=limit&amount="+Lot.toString() + "& price="+priceF.toString() + "& exchange=vipcoin"; Log ((("The following order parameters:"+buyOrders); // Call exchange.IO to directly access the exchange's bulk order interface var ret = exchange.IO (("api", "POST", "orders", buyOrders); Log (("fcoin payment results returned:"+JSON.stringify(ret)); The same goes for false.
The Little DreamThe parameter seems to be incorrect, the parameter is in this form, the parameter name 1 = parameter value 1 & the parameter name 2 = parameter value 2, is a string.
fangzaixiangI've been trying to find out if there's a spelling problem with the exchange.IO call, but it keeps returning false. Calling code: This is a list of all the different ways BuyOrders is credited in the database. Log ((("Parameter of the order to be sold:"+buyOrders); // Call exchange.IO to directly access the exchange's bulk order interface var ret = exchange.IO (("api", "POST", "orders", buyOrders); Log (("fcoin payment results returned:"+JSON.stringify(ret));