aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorMeshCollider <dobsonsa68@gmail.com>2017-07-01 16:00:51 +1200
committerMeshCollider <dobsonsa68@gmail.com>2017-07-01 20:29:00 +1200
commit1d8df01412db0d94ac0030bd2225683891748aff (patch)
tree44364eb67178640bb23a228ce4b567685cd988f6 /doc
parent41f3e84aaca82540582fd5a93fd632e752c3e6bf (diff)
Fix MD formatting in REST-interface.md and spelling mistake in
test_runner.py
Diffstat (limited to 'doc')
-rw-r--r--doc/REST-interface.md12
1 files changed, 6 insertions, 6 deletions
diff --git a/doc/REST-interface.md b/doc/REST-interface.md
index 7fbb174030..dfe218e89f 100644
--- a/doc/REST-interface.md
+++ b/doc/REST-interface.md
@@ -8,14 +8,14 @@ The interface runs on the same port as the JSON-RPC interface, by default port 8
Supported API
-------------
-####Transactions
+#### Transactions
`GET /rest/tx/<TX-HASH>.<bin|hex|json>`
Given a transaction hash: returns a transaction in binary, hex-encoded binary, or JSON formats.
For full TX query capability, one must enable the transaction index via "txindex=1" command line / configuration option.
-####Blocks
+#### Blocks
`GET /rest/block/<BLOCK-HASH>.<bin|hex|json>`
`GET /rest/block/notxdetails/<BLOCK-HASH>.<bin|hex|json>`
@@ -25,12 +25,12 @@ The HTTP request and response are both handled entirely in-memory, thus making m
With the /notxdetails/ option JSON response will only contain the transaction hash instead of the complete transaction details. The option only affects the JSON response.
-####Blockheaders
+#### Blockheaders
`GET /rest/headers/<COUNT>/<BLOCK-HASH>.<bin|hex|json>`
Given a block hash: returns <COUNT> amount of blockheaders in upward direction.
-####Chaininfos
+#### Chaininfos
`GET /rest/chaininfo.json`
Returns various state info regarding block chain processing.
@@ -46,7 +46,7 @@ Only supports JSON as output format.
* pruneheight : (numeric) heighest block available
* softforks : (array) status of softforks in progress
-####Query UTXO set
+#### Query UTXO set
`GET /rest/getutxos/<checkmempool>/<txid>-<n>/<txid>-<n>/.../<txid>-<n>.<bin|hex|json>`
The getutxo command allows querying of the UTXO set given a set of outpoints.
@@ -79,7 +79,7 @@ $ curl localhost:18332/rest/getutxos/checkmempool/b2cdfd7b89def827ff8af7cd9bff76
}
```
-####Memory pool
+#### Memory pool
`GET /rest/mempool/info.json`
Returns various information about the TX mempool.