mirror of
https://github.com/bigchaindb/bigchaindb.git
synced 2024-10-13 13:34:05 +00:00
PR Feedback
This commit is contained in:
parent
93f3e9a06b
commit
284411d881
@ -11,7 +11,7 @@ When you start Bigchaindb using `bigchaindb start`, an HTTP API is exposed at
|
|||||||
the address stored in the BigchainDB node configuration settings. The default
|
the address stored in the BigchainDB node configuration settings. The default
|
||||||
is:
|
is:
|
||||||
|
|
||||||
`http://localhost:9984/api/v1/ <http://localhost:9984/api/v1/>`
|
`http://localhost:9984/api/v1/ <http://localhost:9984/api/v1/>`_
|
||||||
|
|
||||||
but that address can be changed by changing the "API endpoint" configuration
|
but that address can be changed by changing the "API endpoint" configuration
|
||||||
setting (e.g. in a local config file). There's more information about setting
|
setting (e.g. in a local config file). There's more information about setting
|
||||||
@ -294,8 +294,8 @@ GET /unspents/
|
|||||||
a previous transaction and could hence be called unspent conditions/outputs
|
a previous transaction and could hence be called unspent conditions/outputs
|
||||||
(or simply: unspents).
|
(or simply: unspents).
|
||||||
|
|
||||||
This endpoint doesn't return anything if the querystring ``owner_after``
|
This endpoint will return a ``HTTP 400 Bad Request`` if the querystring
|
||||||
happens to not be defined in the request.
|
``owner_after`` happens to not be defined in the request.
|
||||||
|
|
||||||
Note that if unspents for a certain ``owner_after`` have not been found by
|
Note that if unspents for a certain ``owner_after`` have not been found by
|
||||||
the server, this will result in the server returning a 200 OK HTTP status
|
the server, this will result in the server returning a 200 OK HTTP status
|
||||||
@ -303,7 +303,7 @@ GET /unspents/
|
|||||||
|
|
||||||
:param owner_after: A public key, able to validly spend an output of a
|
:param owner_after: A public key, able to validly spend an output of a
|
||||||
transaction, assuming the user also has the corresponding private key.
|
transaction, assuming the user also has the corresponding private key.
|
||||||
:type owner_after: hex string
|
:type owner_after: base58 encoded string
|
||||||
|
|
||||||
**Example request**:
|
**Example request**:
|
||||||
|
|
||||||
|
Loading…
x
Reference in New Issue
Block a user