The field 'user agent' in request header should be 'Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/39.0.2171.71 Safari/537.36'

Composition rules of 'symbol' : 'base-currency' + 'quote-currency'. For 'BTC/USDT' trading,the 'symbol' is eos_btc, and so on.

2.Transaction interface encryption rules

API requests are most likely to be tampered with while being sent over the Internet. To ensure that the request has not been changed, we will ask the user to include a signature in each request (except for the Quote API) to verify that the parameter or parameter value has changed during transmission.
How to sign a request parameter

User-submitted parameters are required to sign in addition to sign.

First, the signature string is required to be sorted by parameter name (comparing the first letter of all parameter names, in abcd order. If the first letters are the same, then it depends on the second letter, and so on, for each of the parameters).

For example: for the following parameters for the signature:

apiKey=376892265asdad5d12726d8bbfbd8912b3&timeStamp=1510235730&nonce=309127&entrustSheetId=123456 Apply for stitching secretKey


sign url : apiKey=376892265asdad5d12726d8bbfbd8912b3&timeStamp=1510235730&nonce=309127&entrustSheetId=123456aQmE8U7bxj16KdJcSd3yX8F8Sakd8aO6LopnHXh27d4kWyb28PxcaTvGrajLDvAw

The "sign" is the must transferred signature parameters.

Finally, the 32-bit md5 algorithm is used to sign the final signature string to get the signature result string (the string is assigned to the parameter sign).

3.Trade limit

Reference related links:https://www.bit-z.pro/tradeLimit

results matching ""

    No results matching ""