diff options
author | Florian Dold <florian.dold@gmail.com> | 2016-01-18 16:23:36 +0100 |
---|---|---|
committer | Florian Dold <florian.dold@gmail.com> | 2016-01-18 16:23:36 +0100 |
commit | 3dc2005d296e72bd4c22e9ccf9dea0ac73dcab01 (patch) | |
tree | da2b795e7d78dc0bf6e1b171057200af002667ab | |
parent | 50aaba11517b67d00819238ac67c6586f469de84 (diff) | |
download | docs-3dc2005d296e72bd4c22e9ccf9dea0ac73dcab01.tar.gz docs-3dc2005d296e72bd4c22e9ccf9dea0ac73dcab01.tar.bz2 docs-3dc2005d296e72bd4c22e9ccf9dea0ac73dcab01.zip |
remove redundant header info
-rw-r--r-- | api-common.rst | 4 | ||||
-rw-r--r-- | api-mint.rst | 8 |
2 files changed, 4 insertions, 8 deletions
diff --git a/api-common.rst b/api-common.rst index a6a41038..d2bf3a50 100644 --- a/api-common.rst +++ b/api-common.rst @@ -93,6 +93,7 @@ Common encodings This section describes how certain types of values are represented throughout the API. .. _base32: +.. _tsref-type-Base32: Binary Data ^^^^^^^^^^^ @@ -104,6 +105,9 @@ Large numbers Large numbers such as RSA blinding factors and 256 bit keys, are transmitted as other binary data in Crockford Base32 encoding. + +.. _tsref-type-Timestamp: + Timestamps ^^^^^^^^^^ Timestamps are represented in JSON as a string literal `"\\/Date(x)\\/"`, where `x` is the decimal representation of the number of seconds past the Unix Epoch (January 1, 1970). The escaped slash (`\\/`) is interpreted in JSON simply as a normal slash, but distinguishes the timestamp from a normal string literal. We use the type "date" in the documentation below. Additionally, the special strings "\\/never\\/" and "\\/forever\\/" are recognized to represent the end of time. diff --git a/api-mint.rst b/api-mint.rst index ce73d31e..9de26fa4 100644 --- a/api-mint.rst +++ b/api-mint.rst @@ -29,7 +29,6 @@ possibly by using HTTPS. The mint responds with a `MintKeysResponse`_ object. :status 200 OK: This request should virtually always be successful. - :resheader Content-Type: application/json **Details:** @@ -197,7 +196,6 @@ Obtaining wire-transfer information **Response:** :status 200: This request should virtually always be successful. - :resheader Content-Type: application/json :Response JSON Object: `WireResponse`_ **Details:** @@ -243,7 +241,6 @@ Obtaining wire-transfer information :status 200: This request should virtually always be successful. :status 501: This wire transfer method is not supported by this mint. - :resheader Content-Type: application/json :Response JSON Object: `WireSepaResponse`_ @@ -305,7 +302,6 @@ mint. :query reserve_pub: EdDSA reserve public key identifying the reserve. :status 200 OK: The reserve was known to the mint, details about it follow in the body. :status 404 Not Found: The withdrawal key does not belong to a reserve known to the mint. - :resheader Content-Type: application/json :Response JSON Object: `ReserveStatus`_ .. _ReserveStatus: @@ -446,9 +442,7 @@ denomination. the digital coins. The request should contain a JSON object with the following fields: - :reqheader Content-Type: application/json :Request JSON Object: `DepositRequest`_ - :resheader Content-Type: application/json :status 200: The operation succeeded, the mint confirms that no double-spending took place. :status 401 Unauthorized: @@ -612,7 +606,6 @@ the API during normal operation. :status 404: the mint does not recognize the denomination key as belonging to the mint, or it has expired - :resheader Content-Type: application/json **Details:** @@ -1436,7 +1429,6 @@ binary-compatible with the implementation of the mint. **Response:** :status 200: the operation succeeded - :resheader Content-Type: application/json .. code-block:: tsref |