Please note that API documentation is only valid for MVS FULL NODE.
You can refer to Metaverse wiki instead as well.
NOTICE
强烈建议使用<a href=/api_v2/>API v2来替代本文档中的API v1.由于历史遗留问题，API v1并不支持JSONRPC2.0标准的返回数据；
核心开发者经过讨论，决定更换boost库json相关的代码, 并且根据命令的使用习惯，重新设计了一版新的API(JSONRPC2.0)，旧的主要接口依然保留，废弃的接口移除；
新的API v2已在v0.7.3发布；
API v1 has some non-standard JSON-RPC reponse, will confused developers.
We found a boost library issue ptree write_json does not conform to JSON standard on json parser.
The Boost write_json method puts quotes around all values, not just strings.So We strongly recommend developers to refer to API-v2:JSON-RPC 2.0.
API(v1) Usage
API URI: /rpc
HTTP Request to local default URL: http://127.0.0.1:8820/rpc
please replace ‘$parameter’ with your own parameter as below.
if we use./mvs-cli $command $param1 $param2 ...
that should be equal as below in RPC-CALL case:
Build Json, then POST to ‘http://127.0.0.1:8820/rpc'{
"method":"$command",
"params":["$param1", "$param2", ...]
}
Obviously, you should use help command for all commands.# see all commands
./mvs-cli help
# see help message of this command
./mvs-cli help $command
Check here for the instance of source codes: https://github.com/ViewBTC/mvs-exchange-tools (keep updating).
Some Documentation For Server Setup in Chinese.
API(v1) Call List
Compatibility after v0.7.3(API v2):
- ○ : keep same name, compatible in
resultif convert to json string. - × : incompatible in
result. - ×× : obliterate.
- newname : rename/alias in API v2, and compatible in
resultif convert to json string.