noripple_check
The noripple_check
command provides a quick way to check the status of the Default Ripple field for an account and the No Ripple flag of its trust lines, compared with the recommended settings.
Request Format
An example of the request format:
The request includes the following parameters:
| Type | Description |
| String | A unique identifier for the account, most commonly the account's address. |
| String | Whether the address refers to a |
| Boolean | [API v1][]: (Optional) If |
| Unsigned Integer | (Optional) The maximum number of trust line problems to include in the results. Defaults to 300. |
| String | (Optional) A 20-byte hex string for the ledger version to use. (See [Specifying Ledgers][]) |
| String or Unsigned Integer | (Optional) The [ledger index][] of the ledger to use, or a shortcut string to choose a ledger automatically. (See [Specifying Ledgers][]) |
Response Format
An example of a successful response:
The response follows the [standard format][], with a successful result containing the following fields:
| Type | Description |
| Number | The [ledger index][] of the ledger used to calculate these results. |
| Array | Array of strings with human-readable descriptions of the problems. This includes up to one entry if the account's Default Ripple setting is not as recommended, plus up to |
| Array | (May be omitted) If the request specified |
Possible Errors
Any of the [universal error types][].
invalidParams
- One or more fields are specified incorrectly, or one or more required fields are missing.actNotFound
- The [Address][] specified in theaccount
field of the request does not correspond to an account in the ledger.lgrNotFound
- The ledger specified by theledger_hash
orledger_index
does not exist, or it does exist but the server does not have it.
Last updated