Interface Description:
  • Bulk revocation limit order
Request URL:
Request Mode:
  • POST
Parameter Required Type Description
apiKey true string ApiKey requested by the user
timeStamp true string Current timestamp
nonce true string Random 6-character string
sign true string signature of the requested parameter
ids true string Order ids 1, 2, 3, 4 separated by commas
How to sign for required parameter:**

All parameters submitted by users except sign require signature.

First, sort signature strings in alphabetical order based on parameters (compare the first letter of all parameter, if they differ, then the string whose first letter comes earlier in the alphabet comes before the other string. If the first letters are the same, then the second letters are compared, and so on).

For example:Sign for the following parameter

timeStamp=1552641715&nonce=ue8jAx&apiKey=17919e05dc57d5d44dccdda03bdd6e2e&coin=usdt&address=1AG1gZvQAYu3WBvgg7p4BvvfNQD2gE693k&number=1000&sign=6932efc6aa44f7605e808bfaa98fd630 and add application secretKey (only needs value, parameter and ‘&” is not required.)

For example:secretKey=aQmE8U7bxj16KdJcSd3yX8F8Sakd8aO6LopnHXh27d4kWyb28PxcaTvGrajLDvAw

Signature string after splicing: timeStamp=1552641715&nonce=ue8jAx&apiKey=17919e05dc57d5d44dccdda03bdd6e2e&coin=usdt&address=1AG1gZvQAYu3WBvJJ7p4BMMfNQD2gE693k&number=1000aQmE8U7bxj16KdJcSd3yX8F8Sakd8aO6LopnHXh27d4kWyb28PxcaTvGrajLDvAw

Note,"sign" is a required parameter.

Last,use md5 32bit algorithm to apply signature algorithm to the parameter, and then generate final signature string (the string assigns value to parameter ‘sign’).

Example of Return Result:
    "status":200, //status code successful
    "msg":"",     //message
                "coin":"bz", //coin
                "over":"100.00000000", //available
                "lock":"-100.00000000" //frozen
    "time":1535525649,  //timestamp
    "microtime":"0.05009400 1535525649", //milliseconds timestamp
    "source":"api"      //source

results matching ""

    No results matching ""