ARCHIVE/xrpl-dev-portal
1
0
Fork 0
mirror of https://github.com/XRPLF/xrpl-dev-portal.git synced 2025-12-06 17:27:57 +00:00
Code Issues Packages Projects Releases Wiki Activity

Referencify the standard response format link

Browse Source
This commit is contained in:
mDuo13
2018-05-11 14:20:35 -07:00
parent a05ecf638f
commit 6afa5ba8a2
52 changed files with 52 additions and 52 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
content/references/rippled-api/admin-rippled-methods/key-generation-methods/validation_create.md
View File

@@ -86,7 +86,7 @@ Connecting to 127.0.0.1:5005
<!-- MULTICODE_BLOCK_END -->
The response follows the [standard format](#response-formatting), with a successful result containing the following fields:
The response follows the [standard format][], with a successful result containing the following fields:
| `Field` | Type | Description |
|:------------------------|:-------|:------------------------------------------|

2
content/references/rippled-api/admin-rippled-methods/key-generation-methods/wallet_propose.md
View File

@@ -164,7 +164,7 @@ Connecting to 127.0.0.1:5005
<!-- MULTICODE_BLOCK_END -->
The response follows the [standard format](#response-formatting), with a successful result containing various important information about the new (potential) account, including the following fields:
The response follows the [standard format][], with a successful result containing various important information about the new (potential) account, including the following fields:
| `Field` | Type | Description |
|:------------------|:-------|:------------------------------------------------|

2
content/references/rippled-api/admin-rippled-methods/logging-and-data-management-methods/can_delete.md
View File

@@ -51,7 +51,7 @@ The request includes the following optional parameter:
If no parameter is specified, no change is made.
The response follows the [standard format](#response-formatting), with
The response follows the [standard format][], with
a successful result containing the following fields:
| `Field` | Type | Description |

2
content/references/rippled-api/admin-rippled-methods/logging-and-data-management-methods/ledger_cleaner.md
View File

@@ -56,7 +56,7 @@ An example of a successful response:
<!-- MULTICODE_BLOCK_END -->
The response follows the [standard format](#response-formatting), with a successful result containing the following fields:
The response follows the [standard format][], with a successful result containing the following fields:
| `Field` | Type | Description |
|:----------|:-------|:---------------------------------|

2
content/references/rippled-api/admin-rippled-methods/logging-and-data-management-methods/ledger_request.md
View File

@@ -39,7 +39,7 @@ You must provide either `ledger_index` or `ledger_hash` but not both.
### Response Format
The response follows the [standard format](#response-formatting). However, the request returns a failure response if it does not have the specified ledger _even if it successfully instructed the `rippled` server to start retrieving the ledger_.
The response follows the [standard format][]. However, the request returns a failure response if it does not have the specified ledger _even if it successfully instructed the `rippled` server to start retrieving the ledger_.
**Note:** To retrieve a ledger, the rippled server must have a direct peer with that ledger in its history. If none of the peers have the requested ledger, you can use the [`connect` command](#connect) or the `fixed_ips` section of the config file to add Ripple's full-history server at `s2.ripple.com` and then make the `ledger_request` request again.

2
content/references/rippled-api/admin-rippled-methods/logging-and-data-management-methods/log_level.md
View File

@@ -121,7 +121,7 @@ Connecting to 127.0.0.1:5005
<!-- MULTICODE_BLOCK_END -->
The response follows the [standard format](#response-formatting). The response format depends on whether the request specified a `severity`. If it did, the log level is changed and a successful result contains no additional fields.
The response follows the [standard format][]. The response format depends on whether the request specified a `severity`. If it did, the log level is changed and a successful result contains no additional fields.
Otherwise, the request contains the following field:

2
content/references/rippled-api/admin-rippled-methods/logging-and-data-management-methods/logrotate.md
View File

@@ -64,7 +64,7 @@ Connecting to 127.0.0.1:5005
<!-- MULTICODE_BLOCK_END -->
The response follows the [standard format](#response-formatting), with a successful result containing the following fields:
The response follows the [standard format][], with a successful result containing the following fields:
| `Field` | Type | Description |
|:----------|:-------|:--------------------------------------------------------|

2
content/references/rippled-api/admin-rippled-methods/server-control-methods/connect.md
View File

@@ -83,7 +83,7 @@ Connecting to 127.0.0.1:5005
<!-- MULTICODE_BLOCK_END -->
The response follows the [standard format](#response-formatting), with a successful result containing the following fields:
The response follows the [standard format][], with a successful result containing the following fields:
| `Field` | Type | Description |
|:----------|:-------|:-------------------------------------------------------|

2
content/references/rippled-api/admin-rippled-methods/server-control-methods/ledger_accept.md
View File

@@ -45,7 +45,7 @@ An example of a successful response:
}
```
The response follows the [standard format](#response-formatting), with a successful result containing the following field:
The response follows the [standard format][], with a successful result containing the following field:
| `Field` | Type | Description |
|:-----------------------|:-----------------|:---------------------------------|

2
content/references/rippled-api/admin-rippled-methods/server-control-methods/stop.md
View File

@@ -72,7 +72,7 @@ Connecting to 127.0.0.1:5005
<!-- MULTICODE_BLOCK_END -->
The response follows the [standard format](#response-formatting), with a successful result containing the following fields:
The response follows the [standard format][], with a successful result containing the following fields:
| `Field` | Type | Description |
|:----------|:-------|:-------------------------------------|

2
content/references/rippled-api/admin-rippled-methods/server-control-methods/validation_seed.md
View File

@@ -72,7 +72,7 @@ Connecting to 127.0.0.1:5005
<!-- MULTICODE_BLOCK_END -->
The response follows the [standard format](#response-formatting), with a successful result containing the following fields:
The response follows the [standard format][], with a successful result containing the following fields:
| `Field` | Type | Description |
|:------------------------|:-------|:------------------------------------------|

2
content/references/rippled-api/admin-rippled-methods/status-and-debugging-methods/consensus_info.md
View File

@@ -201,7 +201,7 @@ Connecting to 127.0.0.1:5005
<!-- MULTICODE_BLOCK_END -->
The response follows the [standard format](#response-formatting), with a successful result containing the following fields:
The response follows the [standard format][], with a successful result containing the following fields:
| `Field` | Type | Description |
|:--------|:-------|:----------------------------------------------------------|

2
content/references/rippled-api/admin-rippled-methods/status-and-debugging-methods/feature.md
View File

@@ -171,7 +171,7 @@ Connecting to 127.0.0.1:5005
<!-- MULTICODE_BLOCK_END -->
The response follows the [standard format](#response-formatting), with a successful result containing **a map of amendments** as a JSON object. The keys of the object are amendment IDs. The values for each key are _amendment objects_ that describe the status of the amendment with that ID. If the request specified a `feature`, the map contains only the requested amendment object, after applying any changes from the request. Each amendment object has the following fields:
The response follows the [standard format][], with a successful result containing **a map of amendments** as a JSON object. The keys of the object are amendment IDs. The values for each key are _amendment objects_ that describe the status of the amendment with that ID. If the request specified a `feature`, the map contains only the requested amendment object, after applying any changes from the request. Each amendment object has the following fields:
| `Field` | Type | Description |
|:------------|:--------|:-----------------------------------------------------|

2
content/references/rippled-api/admin-rippled-methods/status-and-debugging-methods/fetch_info.md
View File

@@ -134,7 +134,7 @@ Connecting to 127.0.0.1:5005
<!-- MULTICODE_BLOCK_END -->
The response follows the [standard format](#response-formatting), with a successful result containing the following fields:
The response follows the [standard format][], with a successful result containing the following fields:
| `Field` | Type | Description |
|:--------|:-------|:----------------------------------------------------------|

2
content/references/rippled-api/admin-rippled-methods/status-and-debugging-methods/get_counts.md
View File

@@ -132,7 +132,7 @@ Connecting to 127.0.0.1:5005
<!-- MULTICODE_BLOCK_END -->
The response follows the [standard format](#response-formatting). The list of fields contained in the result is subject to change without notice, but it may contain any of the following (among others):
The response follows the [standard format][]. The list of fields contained in the result is subject to change without notice, but it may contain any of the following (among others):
| `Field` | Type | Description |
|:--------------|:-------|:----------------------------------------------------|

2
content/references/rippled-api/admin-rippled-methods/status-and-debugging-methods/peers.md
View File

@@ -370,7 +370,7 @@ Connecting to 127.0.0.1:5005
<!-- MULTICODE_BLOCK_END -->
The response follows the [standard format](#response-formatting), with a successful result containing a JSON object with the following fields:
The response follows the [standard format][], with a successful result containing a JSON object with the following fields:
| `Field` | Type | Description |
|:----------|:-------|:--------------------------------------------------------|

2
content/references/rippled-api/admin-rippled-methods/status-and-debugging-methods/print.md
View File

@@ -224,7 +224,7 @@ Connecting to 127.0.0.1:5005
<!-- MULTICODE_BLOCK_END -->
The response follows the [standard format](#response-formatting). Additional fields in the result depend on the internal state of the `rippled` server. The results of this command are subject to change without notice.
The response follows the [standard format][]. Additional fields in the result depend on the internal state of the `rippled` server. The results of this command are subject to change without notice.
### Possible Errors

2
content/references/rippled-api/admin-rippled-methods/status-and-debugging-methods/validator_list_sites.md
View File

@@ -109,7 +109,7 @@ Connecting to 127.0.0.1:5005
<!-- MULTICODE_BLOCK_END -->
The response follows the [standard format](#response-formatting), with a successful result containing the following field:
The response follows the [standard format][], with a successful result containing the following field:
| `Field` | Type | Description |
|:------------------|:------|----------------------------------|

2
content/references/rippled-api/admin-rippled-methods/status-and-debugging-methods/validators.md
View File

@@ -150,7 +150,7 @@ Connecting to 127.0.0.1:5005
<!-- MULTICODE_BLOCK_END -->
The response follows the [standard format](#response-formatting), with a successful result containing the following fields:
The response follows the [standard format][], with a successful result containing the following fields:
| `Field` | Type | Description |
|:-------------------------|:-------|:-----------------------------------------|