HTTP REST updates

- Updated all requests with Dash examples
 - Updated all requests to add/remove fields to match Dash
This commit is contained in:
thephez 2017-12-06 17:29:20 -05:00
parent 6fd6f8b8ab
commit 7f27d1013b
11 changed files with 488 additions and 408 deletions

View file

@ -6,17 +6,16 @@ http://opensource.org/licenses/MIT.
### HTTP REST
{% include helpers/subhead-links.md %}
<!-- __ -->
{% autocrossref %}
As of [version 0.10.0][bitcoin core 0.10.0], Bitcoin Core provides
an **unauthenticated** HTTP REST interface. The interface runs on the
same port as the JSON-RPC interface, by default port 8332 for mainnet and
port 18332 for testnet. It must be enabled by either starting Bitcoin
Dash Core provides an **unauthenticated** HTTP REST interface. The interface
runs on the same port as the JSON-RPC interface, by default port 9998 for
mainnet and port 19998 for testnet. It must be enabled by either starting Dash
Core with the `-rest` option or by specifying `rest=1` in the
configuration file. Make sure that the RPC interface is also activated.
Set `server=1` in `bitcoin.conf` or supply the `-server` argument when
starting Bitcoin Core. Starting Bitcoin Core with `bitcoind` automatically
Set `server=1` in `dash.conf` or supply the `-server` argument when
starting Dash Core. Starting Dash Core with `dashd` automatically
enables the RPC interface.
The interface is not intended for public access and is only accessible
@ -26,7 +25,7 @@ from localhost by default.
localhost, possibly allowing third parties to use cross-site scripting
attacks to download your transaction and block data, reducing your
privacy. If you have privacy concerns, you should not run a browser on
the same computer as a REST-enabled Bicoin Core node.
the same computer as a REST-enabled Dash Core node.
The interface uses standard [HTTP status
codes](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes) and