DirectkitJSON and DirectkitJSON2

This document means only for DirectkitJSON users. It is not needed if you have already used DirectkitJSON2.

Differences

 DirectkitJSON2 (recommended)DirectkitJSON (deprecated)
URLhttps://.../directkitjson2/service.asmxhttps://.../directkitjson/service.asmx
Request

{

    "p":{   
        "wlPass":"string",
        "wlLogin":"string",
        "language":" string ",
        "version":" string ",
        "walletIp":" string ",
        "walletUa":"string"
        ...
    }

}

  • Optional parameters might not present in the request.
  • To migrate from directkitjson to directjson2, you have to change the request format: adding the "p" wrapper. It is the only change you will have to do in your codes..

{

    "wlPass":"string",
    "wlLogin":"string",
    "language":" string ",
    "version":" string ",
    "walletIp":" string ",
    "walletUa":"string"
    ...

}

All the possible parameters must to be present in the request. Optional parameters could have empty value, though they must to be present in the request.

 Response  identical

Why directkitjson2

  • More secure: the wrapper "p" of the requests prevents json hijacking. the same reason for the wrapper "d" of the responses.
  • In the old directkitjson, all the possible parameters must to be present in the request. If the new API version add more (optional) parameters, it will break backward-compatibility. The new directkitjson2 removed this handicap.
  • The directkitjson is no longer supported, new features and new parameters will be added to only directkitjson2.

 

Search