From 005a164e6b86174719a6cf0a2fa31c937f9a1072 Mon Sep 17 00:00:00 2001 From: diminator Date: Thu, 5 Jan 2017 15:15:17 +0100 Subject: [PATCH] additional info on INVALID block --- .../server/source/drivers-clients/http-client-server-api.rst | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/docs/server/source/drivers-clients/http-client-server-api.rst b/docs/server/source/drivers-clients/http-client-server-api.rst index 3a3bdd71..f60c5f0e 100644 --- a/docs/server/source/drivers-clients/http-client-server-api.rst +++ b/docs/server/source/drivers-clients/http-client-server-api.rst @@ -303,12 +303,13 @@ Blocks Get the block with the ID ``block_id``. .. note:: - As ``status``'s default value is set to ``VALID``, only ``VALID`` blocks + As ``status``'s default value is set to ``VALID``, hence only ``VALID`` blocks will be returned by this endpoint. In case ``status=VALID``, but a block that was labeled ``UNDECIDED`` or ``INVALID`` is requested by ``block_id``, this endpoint will return a ``404 Not Found`` status code to warn the user. To check a block's status independently, use the - `Statuses endpoint <#get--statuses-tx_id|block_id>`_. + `Statuses endpoint <#get--statuses-tx_id|block_id>`_. The ``INVALID`` status + can be handy to figure out why the block was rejected. :param block_id: block ID :type block_id: hex string