From fb5b310443d6563095bf5c1debe0f0a22a3d21f3 Mon Sep 17 00:00:00 2001
From: mDuo13 <mduo13@gmail.com>
Date: Thu, 18 Sep 2014 13:52:08 -0700
Subject: [PATCH] [DOC] ripd status updates

---
 rippled-apis.html | 136 +++++++++++++++++++++++++++++-----------------
 websocket_api.md  |  11 +++-
 2 files changed, 94 insertions(+), 53 deletions(-)

diff --git a/rippled-apis.html b/rippled-apis.html
index 475723b303..c06ef03f44 100644
--- a/rippled-apis.html
+++ b/rippled-apis.html
@@ -62,7 +62,7 @@ mixpanel.init("132d42885e094171f34467fc54da6fab");
   
   <!-- syntax selection js -->
   <script src="js/multicodetab.js"></script>
-  <!-- Code to load Flatdoc; commented out on compiled page  -->
+  <!-- Code to load Flatdoc; commented out on compiled page  
   <script>
     $(".flatdoc-content").empty();
     $(".content-root .menubar .menu").empty();
@@ -72,7 +72,7 @@ mixpanel.init("132d42885e094171f34467fc54da6fab");
     $(document).on('flatdoc:ready', $().multicode_tabs);
   </script>
   <!-- end flatdoc load -->
-  <!-- Alternate multicode tabs for compiled page: 
+  <!-- Alternate multicode tabs for compiled page: -->
   <script>
     $(document).ready(function() {
         $(".multicode").minitabs()
@@ -113,25 +113,23 @@ mixpanel.init("132d42885e094171f34467fc54da6fab");
         </div><!--/.nav-collapse -->
       </div>
     </div>
-<!-- 
-  <div class="header-subnav-wrapper">
-  <div class='header-subnav navbar-fixed-top'>
-    <ul>
-        <li><a href='?p=introduction' id='subnav-intro'>Introduction</a></li>
-        <li><a href='?p=ripple-rest-api' id='subnav-rest'>Ripple-REST API</a></li>
-        <li><a href='?p=web-sockets-api' id='subnav-websocket'>WebSocket &amp; JSON-RPC APIs</a></li>
-    </ul>
-    <div class='clearer'>&nbsp;</div>
-  </div>
-</div>
- -->
+    
+    
   <div class="content-root">
     <div class="menubar">
 
-      <div class="menu section" role="flatdoc-menu"><ul><li class="level-0" id="root-item"><ul id="root-list" class="level-1"><li class="level-1" id="websocket-and-json-rpc-apis-item"><a class="level-1" href="#websocket-and-json-rpc-apis" id="websocket-and-json-rpc-apis-link">WebSocket and JSON-RPC APIs</a><ul id="websocket-and-json-rpc-apis-list" class="level-2"><li class="level-2" id="changes-to-the-apis-item"><a class="level-2" href="#changes-to-the-apis" id="changes-to-the-apis-link">Changes to the APIs</a></li><li class="level-2" id="connecting-to-rippled-item"><a class="level-2" href="#connecting-to-rippled" id="connecting-to-rippled-link">Connecting to rippled</a><ul id="connecting-to-rippled-list" class="level-3"><li class="level-3" id="reasons-to-run-your-own-rippled-item"><a class="level-3" href="#reasons-to-run-your-own-rippled" id="reasons-to-run-your-own-rippled-link">Reasons to Run Your Own rippled</a></li><li class="level-3" id="websocket-api-item"><a class="level-3" href="#websocket-api" id="websocket-api-link">WebSocket API</a></li><li class="level-3" id="json-rpc-item"><a class="level-3" href="#json-rpc" id="json-rpc-link">JSON-RPC</a></li><li class="level-3" id="commandline-item"><a class="level-3" href="#commandline" id="commandline-link">Commandline</a></li></ul></li><li class="level-2" id="request-formatting-item"><a class="level-2" href="#request-formatting" id="request-formatting-link">Request Formatting</a></li><li class="level-2" id="response-formatting-item"><a class="level-2" href="#response-formatting" id="response-formatting-link">Response Formatting</a></li><li class="level-2" id="error-responses-item"><a class="level-2" href="#error-responses" id="error-responses-link">Error Responses</a><ul id="error-responses-list" class="level-3"><li class="level-3" id="caution-on-errors-item"><a class="level-3" href="#caution-on-errors" id="caution-on-errors-link">Caution on Errors</a></li></ul></li><li class="level-2" id="formatting-conventions-item"><a class="level-2" href="#formatting-conventions" id="formatting-conventions-link">Formatting Conventions</a><ul id="formatting-conventions-list" class="level-3"><li class="level-3" id="unique-identifiers-item"><a class="level-3" href="#unique-identifiers" id="unique-identifiers-link">Unique Identifiers</a></li><li class="level-3" id="specifying-a-ledger-instance-item"><a class="level-3" href="#specifying-a-ledger-instance" id="specifying-a-ledger-instance-link">Specifying a Ledger Instance</a></li><li class="level-3" id="specifying-currency-amounts-item"><a class="level-3" href="#specifying-currency-amounts" id="specifying-currency-amounts-link">Specifying Currency Amounts</a></li><li class="level-3" id="specifying-time-item"><a class="level-3" href="#specifying-time" id="specifying-time-link">Specifying Time</a></li><li class="level-3" id="possible-server-states-item"><a class="level-3" href="#possible-server-states" id="possible-server-states-link">Possible Server States</a></li></ul></li></ul></li><li class="level-1" id="api-methods-item"><a class="level-1" href="#api-methods" id="api-methods-link">API Methods</a><ul id="api-methods-list" class="level-2"><li class="level-2" id="list-of-public-commands-item"><a class="level-2" href="#list-of-public-commands" id="list-of-public-commands-link">List of Public Commands</a></li><li class="level-2" id="admin-commands-item"><a class="level-2" href="#admin-commands" id="admin-commands-link">Admin Commands</a></li><li class="level-2" id="commandline-access-item"><a class="level-2" href="#commandline-access" id="commandline-access-link">Commandline Access</a></li></ul></li><li class="level-1" id="managing-accounts-item"><a class="level-1" href="#managing-accounts" id="managing-accounts-link">Managing Accounts</a><ul id="managing-accounts-list" class="level-2"><li class="level-2" id="account-info-item"><a class="level-2 active" href="#account-info" id="account-info-link">account_info</a></li><li class="level-2" id="account-lines-item"><a class="level-2" href="#account-lines" id="account-lines-link">account_lines</a></li><li class="level-2" id="account-offers-item"><a class="level-2" href="#account-offers" id="account-offers-link">account_offers</a></li><li class="level-2" id="account-tx-item"><a class="level-2" href="#account-tx" id="account-tx-link">account_tx</a></li><li class="level-2" id="wallet-propose-item"><a class="level-2" href="#wallet-propose" id="wallet-propose-link">wallet_propose</a></li></ul></li><li class="level-1" id="managing-ledgers-item"><a class="level-1" href="#managing-ledgers" id="managing-ledgers-link">Managing Ledgers</a><ul id="managing-ledgers-list" class="level-2"><li class="level-2" id="ledger-item"><a class="level-2" href="#ledger" id="ledger-link">ledger</a></li><li class="level-2" id="ledger-closed-item"><a class="level-2" href="#ledger-closed" id="ledger-closed-link">ledger_closed</a></li><li class="level-2" id="ledger-current-item"><a class="level-2" href="#ledger-current" id="ledger-current-link">ledger_current</a></li><li class="level-2" id="ledger-data-item"><a class="level-2" href="#ledger-data" id="ledger-data-link">ledger_data</a></li><li class="level-2" id="ledger-entry-item"><a class="level-2" href="#ledger-entry" id="ledger-entry-link">ledger_entry</a></li></ul></li><li class="level-1" id="managing-transactions-item"><a class="level-1" href="#managing-transactions" id="managing-transactions-link">Managing Transactions</a><ul id="managing-transactions-list" class="level-2"><li class="level-2" id="tx-item"><a class="level-2" href="#tx" id="tx-link">tx</a></li><li class="level-2" id="transaction-entry-item"><a class="level-2" href="#transaction-entry" id="transaction-entry-link">transaction_entry</a></li><li class="level-2" id="tx-history-item"><a class="level-2" href="#tx-history" id="tx-history-link">tx_history</a></li><li class="level-2" id="path-find-item"><a class="level-2" href="#path-find" id="path-find-link">path_find</a><ul id="path-find-list" class="level-3"><li class="level-3" id="path-find-create-item"><a class="level-3" href="#path-find-create" id="path-find-create-link">path_find create</a></li><li class="level-3" id="path-find-close-item"><a class="level-3" href="#path-find-close" id="path-find-close-link">path_find close</a></li><li class="level-3" id="path-find-status-item"><a class="level-3" href="#path-find-status" id="path-find-status-link">path_find status</a></li></ul></li><li class="level-2" id="ripple-path-find-item"><a class="level-2" href="#ripple-path-find" id="ripple-path-find-link">ripple_path_find</a></li><li class="level-2" id="sign-item"><a class="level-2" href="#sign" id="sign-link">sign</a></li><li class="level-2" id="submit-item"><a class="level-2" href="#submit" id="submit-link">submit</a></li><li class="level-2" id="book-offers-item"><a class="level-2" href="#book-offers" id="book-offers-link">book_offers</a></li></ul></li><li class="level-1" id="subscriptions-item"><a class="level-1" href="#subscriptions" id="subscriptions-link">Subscriptions</a><ul id="subscriptions-list" class="level-2"><li class="level-2" id="subscribe-item"><a class="level-2" href="#subscribe" id="subscribe-link">subscribe</a><ul id="subscribe-list" class="level-3"><li class="level-3" id="subscription-stream-messages-item"><a class="level-3" href="#subscription-stream-messages" id="subscription-stream-messages-link">Subscription Stream Messages</a></li></ul></li><li class="level-2" id="unsubscribe-item"><a class="level-2" href="#unsubscribe" id="unsubscribe-link">unsubscribe</a></li></ul></li><li class="level-1" id="server-information-item"><a class="level-1" href="#server-information" id="server-information-link">Server Information</a><ul id="server-information-list" class="level-2"><li class="level-2" id="server-info-item"><a class="level-2" href="#server-info" id="server-info-link">server_info</a></li><li class="level-2" id="server-state-item"><a class="level-2" href="#server-state" id="server-state-link">server_state</a></li></ul></li><li class="level-1" id="convenience-functions-item"><a class="level-1" href="#convenience-functions" id="convenience-functions-link">Convenience Functions</a><ul id="convenience-functions-list" class="level-2"><li class="level-2" id="ping-item"><a class="level-2" href="#ping" id="ping-link">ping</a></li><li class="level-2" id="random-item"><a class="level-2" href="#random" id="random-link">random</a></li><li class="level-2" id="json-item"><a class="level-2" href="#json" id="json-link">json</a></li></ul></li></ul></li></ul></div>
-    
+      <div class="menu section" role="flatdoc-menu">
+      
+      
+<ul><li class="level-0" id="root-item"><ul id="root-list" class="level-1"><li class="level-1" id="websocket-and-json-rpc-apis-item"><a class="level-1" href="#websocket-and-json-rpc-apis" id="websocket-and-json-rpc-apis-link">WebSocket and JSON-RPC APIs</a><ul id="websocket-and-json-rpc-apis-list" class="level-2"><li class="level-2" id="changes-to-the-apis-item"><a class="level-2" href="#changes-to-the-apis" id="changes-to-the-apis-link">Changes to the APIs</a></li><li class="level-2" id="connecting-to-rippled-item"><a class="level-2" href="#connecting-to-rippled" id="connecting-to-rippled-link">Connecting to rippled</a><ul id="connecting-to-rippled-list" class="level-3"><li class="level-3" id="reasons-to-run-your-own-rippled-item"><a class="level-3" href="#reasons-to-run-your-own-rippled" id="reasons-to-run-your-own-rippled-link">Reasons to Run Your Own rippled</a></li><li class="level-3" id="websocket-api-item"><a class="level-3" href="#websocket-api" id="websocket-api-link">WebSocket API</a></li><li class="level-3" id="json-rpc-item"><a class="level-3" href="#json-rpc" id="json-rpc-link">JSON-RPC</a></li><li class="level-3" id="commandline-item"><a class="level-3" href="#commandline" id="commandline-link">Commandline</a></li></ul></li><li class="level-2" id="request-formatting-item"><a class="level-2" href="#request-formatting" id="request-formatting-link">Request Formatting</a></li><li class="level-2" id="response-formatting-item"><a class="level-2" href="#response-formatting" id="response-formatting-link">Response Formatting</a></li><li class="level-2" id="error-responses-item"><a class="level-2" href="#error-responses" id="error-responses-link">Error Responses</a><ul id="error-responses-list" class="level-3"><li class="level-3" id="caution-on-errors-item"><a class="level-3" href="#caution-on-errors" id="caution-on-errors-link">Caution on Errors</a></li></ul></li><li class="level-2" id="formatting-conventions-item"><a class="level-2" href="#formatting-conventions" id="formatting-conventions-link">Formatting Conventions</a><ul id="formatting-conventions-list" class="level-3"><li class="level-3" id="unique-identifiers-item"><a class="level-3" href="#unique-identifiers" id="unique-identifiers-link">Unique Identifiers</a></li><li class="level-3" id="specifying-a-ledger-instance-item"><a class="level-3" href="#specifying-a-ledger-instance" id="specifying-a-ledger-instance-link">Specifying a Ledger Instance</a></li><li class="level-3" id="specifying-currency-amounts-item"><a class="level-3" href="#specifying-currency-amounts" id="specifying-currency-amounts-link">Specifying Currency Amounts</a></li><li class="level-3" id="specifying-time-item"><a class="level-3" href="#specifying-time" id="specifying-time-link">Specifying Time</a></li><li class="level-3" id="possible-server-states-item"><a class="level-3" href="#possible-server-states" id="possible-server-states-link">Possible Server States</a></li></ul></li></ul></li><li class="level-1" id="api-methods-item"><a class="level-1" href="#api-methods" id="api-methods-link">API Methods</a><ul id="api-methods-list" class="level-2"><li class="level-2" id="list-of-public-commands-item"><a class="level-2" href="#list-of-public-commands" id="list-of-public-commands-link">List of Public Commands</a></li><li class="level-2" id="admin-commands-item"><a class="level-2" href="#admin-commands" id="admin-commands-link">Admin Commands</a></li><li class="level-2" id="commandline-access-item"><a class="level-2" href="#commandline-access" id="commandline-access-link">Commandline Access</a></li></ul></li><li class="level-1" id="managing-accounts-item"><a class="level-1" href="#managing-accounts" id="managing-accounts-link">Managing Accounts</a><ul id="managing-accounts-list" class="level-2"><li class="level-2" id="account-info-item"><a class="level-2" href="#account-info" id="account-info-link">account_info</a></li><li class="level-2" id="account-lines-item"><a class="level-2" href="#account-lines" id="account-lines-link">account_lines</a></li><li class="level-2" id="account-offers-item"><a class="level-2" href="#account-offers" id="account-offers-link">account_offers</a></li><li class="level-2" id="account-tx-item"><a class="level-2" href="#account-tx" id="account-tx-link">account_tx</a></li><li class="level-2" id="wallet-propose-item"><a class="level-2" href="#wallet-propose" id="wallet-propose-link">wallet_propose</a></li></ul></li><li class="level-1" id="managing-ledgers-item"><a class="level-1" href="#managing-ledgers" id="managing-ledgers-link">Managing Ledgers</a><ul id="managing-ledgers-list" class="level-2"><li class="level-2" id="ledger-item"><a class="level-2" href="#ledger" id="ledger-link">ledger</a></li><li class="level-2" id="ledger-closed-item"><a class="level-2" href="#ledger-closed" id="ledger-closed-link">ledger_closed</a></li><li class="level-2" id="ledger-current-item"><a class="level-2" href="#ledger-current" id="ledger-current-link">ledger_current</a></li><li class="level-2" id="ledger-data-item"><a class="level-2" href="#ledger-data" id="ledger-data-link">ledger_data</a></li><li class="level-2" id="ledger-entry-item"><a class="level-2" href="#ledger-entry" id="ledger-entry-link">ledger_entry</a></li></ul></li><li class="level-1" id="managing-transactions-item"><a class="level-1" href="#managing-transactions" id="managing-transactions-link">Managing Transactions</a><ul id="managing-transactions-list" class="level-2"><li class="level-2" id="tx-item"><a class="level-2" href="#tx" id="tx-link">tx</a></li><li class="level-2" id="transaction-entry-item"><a class="level-2" href="#transaction-entry" id="transaction-entry-link">transaction_entry</a></li><li class="level-2" id="tx-history-item"><a class="level-2" href="#tx-history" id="tx-history-link">tx_history</a></li><li class="level-2" id="path-find-item"><a class="level-2" href="#path-find" id="path-find-link">path_find</a><ul id="path-find-list" class="level-3"><li class="level-3" id="path-find-create-item"><a class="level-3" href="#path-find-create" id="path-find-create-link">path_find create</a></li><li class="level-3" id="path-find-close-item"><a class="level-3" href="#path-find-close" id="path-find-close-link">path_find close</a></li><li class="level-3" id="path-find-status-item"><a class="level-3" href="#path-find-status" id="path-find-status-link">path_find status</a></li></ul></li><li class="level-2" id="ripple-path-find-item"><a class="level-2" href="#ripple-path-find" id="ripple-path-find-link">ripple_path_find</a></li><li class="level-2" id="sign-item"><a class="level-2" href="#sign" id="sign-link">sign</a></li><li class="level-2" id="submit-item"><a class="level-2" href="#submit" id="submit-link">submit</a></li><li class="level-2" id="book-offers-item"><a class="level-2" href="#book-offers" id="book-offers-link">book_offers</a></li></ul></li><li class="level-1" id="subscriptions-item"><a class="level-1" href="#subscriptions" id="subscriptions-link">Subscriptions</a><ul id="subscriptions-list" class="level-2"><li class="level-2" id="subscribe-item"><a class="level-2" href="#subscribe" id="subscribe-link">subscribe</a><ul id="subscribe-list" class="level-3"><li class="level-3" id="subscription-stream-messages-item"><a class="level-3" href="#subscription-stream-messages" id="subscription-stream-messages-link">Subscription Stream Messages</a></li></ul></li><li class="level-2" id="unsubscribe-item"><a class="level-2" href="#unsubscribe" id="unsubscribe-link">unsubscribe</a></li></ul></li><li class="level-1" id="server-information-item"><a class="level-1" href="#server-information" id="server-information-link">Server Information</a><ul id="server-information-list" class="level-2"><li class="level-2" id="server-info-item"><a class="level-2" href="#server-info" id="server-info-link">server_info</a></li><li class="level-2" id="server-state-item"><a class="level-2" href="#server-state" id="server-state-link">server_state</a></li></ul></li><li class="level-1" id="convenience-functions-item"><a class="level-1" href="#convenience-functions" id="convenience-functions-link">Convenience Functions</a><ul id="convenience-functions-list" class="level-2"><li class="level-2" id="ping-item"><a class="level-2" href="#ping" id="ping-link">ping</a></li><li class="level-2" id="random-item"><a class="level-2" href="#random" id="random-link">random</a></li><li class="level-2" id="json-item"><a class="level-2" href="#json" id="json-link">json</a></li></ul></li></ul></li></ul>
+      
+      
+      
+      </div>
     </div>
     <div role="flatdoc-content" class="content">
+    
+    
     <h1 id="websocket-and-json-rpc-apis">WebSocket and JSON-RPC APIs</h1><p>If you want to communicate directly with the <code title="Double-click to expand/collapse">rippled</code> server, you have three fairly similar options for how to do that. All of these APIs use the same list of commands, with almost entirely the same parameters in each command. Whereas the <a href="?p=ripple-rest-api">Ripple-REST API</a> provides a simplified interface on top of the WebSocket API for easier integration, these APIs provide the full power of Ripple but require slightly more complexity:</p><ul>
 <li>The WebSocket API uses the <a href="http://www.html5rocks.com/en/tutorials/websockets/basics/">WebSocket protocol</a>, available in most browsers and Javascript implementations, to achieve persistent two-way communication. There is not a 1:1 correlation between requests and responses. Some requests prompt the server to send multiple messages back asynchronously; other times, responses may arrive in a different order than the requests that prompted them. </li>
 <li>The JSON-RPC API relies on simple request-response communication via HTTP. For commands that prompt multiple responses, you can provide a callback URL.</li>
@@ -482,7 +480,7 @@ Null method</code></pre><p>For other errors that returned with HTTP status code
 </tr>
 </tbody>
 </table><p><em>Note:</em> The distinction between <code title="Double-click to expand/collapse">full</code>, <code title="Double-click to expand/collapse">validating</code>, and <code title="Double-click to expand/collapse">proposing</code> is based on synchronization with the rest of the global network, and it is normal for a server to fluctuate between these states as a course of general operation.</p><h1 id="api-methods">API Methods</h1><p>API methods for the Websocket and JSON-RPC APIs are defined by command names, and are divided into Public Commands and Admin Commands. Public Commands are not necessarily meant for the general public, but they are used by any client attached to the server. (Think of Public Commands as being for members or customers of the organization running the server, while the Admin Commands are for the personnel in charge of keeping the server operational.) Public Commands include the general operations for Ripple use, including checking the state of the ledger, finding a path to connecting users, and submitting a transaction, among others. Admin Commands, on the other hand, are meant only for the operators of the server, and include commands for managing the state of the server, the nodes it uses for validation, and other administrative features.</p><p>This page deals with all the Public Commands available. </p><h2 id="list-of-public-commands">List of Public Commands</h2><ul>
-<li><a class="active" href="#account-info"><code title="Double-click to expand/collapse">account_info</code> - Get basic data about an account</a></li>
+<li><a href="#account-info"><code title="Double-click to expand/collapse">account_info</code> - Get basic data about an account</a></li>
 <li><a href="#account-lines"><code title="Double-click to expand/collapse">account_lines</code> - Get info about an account’s trust lines</a></li>
 <li><a href="#account-offers"><code title="Double-click to expand/collapse">account_offers</code> - Get info about an account’s currency exchange offers</a></li>
 <li><a href="#account-tx"><code title="Double-click to expand/collapse">account_tx</code> - Get info about an account’s transactions</a></li>
@@ -509,7 +507,7 @@ Null method</code></pre><p>For other errors that returned with HTTP status code
 <li><a href="#wallet-propose"><code title="Double-click to expand/collapse">wallet_propose</code> - Generate keys for a new account</a></li>
 </ul><p>For information about other Admin Commands, consult <a href="https://ripple.com/wiki/JSON_Messages">the old wiki documentation</a>.</p><h2 id="commandline-access">Commandline Access</h2><p>The <code title="Double-click to expand/collapse">rippled</code> application, in addition to acting as a server, can be run (as a separate instance) to act as a JSON-RPC client. In this mode, it has syntax for triggering most API methods with a single line from the command prompt, as described in each method. However, some methods don’t have a commandline shortcut, so it also provides the following catch-all method for performing commands:</p><ul>
 <li><a href="#json"><code title="Double-click to expand/collapse">json</code> - Pass JSON through the commandline</a></li>
-</ul><h1 id="managing-accounts">Managing Accounts</h1><p>Accounts are the core unit of authentication in the Ripple Network. Each account can hold balances in multiple currencies, and all transactions must be signed by an account’s secret key. In order for an account to exist in a validated ledger version, it must hold a minimum reserve amount of XRP. (The <a href="https://ripple.com/wiki/Reserves">reserve for an account</a> increases with the amount of data it is responsible for in the shared ledger.) It is expected that accounts will correspond loosely to individual users. </p><h2 id="account-info">account_info</h2><p>The <code title="Double-click to expand/collapse">account_info</code> command retrieves information about an account, its activity, and its XRP balance. All information retrieved is relative to a particular version of the ledger. </p><h4>Request Format</h4><p>An example of an account_info request:</p><div id="code-3" class="multicode"><ul class="codetabs"><li><a class="current" href="#code-3-0">WebSocket</a></li><li><a href="#code-3-1">JSON-RPC</a></li><li><a href="#code-3-2">Commandline</a></li></ul>
+</ul><h1 id="managing-accounts">Managing Accounts</h1><p>Accounts are the core unit of authentication in the Ripple Network. Each account can hold balances in multiple currencies, and all transactions must be signed by an account’s secret key. In order for an account to exist in a validated ledger version, it must hold a minimum reserve amount of XRP. (The <a href="https://ripple.com/wiki/Reserves">reserve for an account</a> increases with the amount of data it is responsible for in the shared ledger.) It is expected that accounts will correspond loosely to individual users. </p><h2 id="account-info">account_info</h2><p><a href="https://github.com/ripple/rippled/blob/master/src/ripple/module/rpc/handlers/AccountInfo.cpp" title="Source">[Source]<br></a></p><p>The <code title="Double-click to expand/collapse">account_info</code> command retrieves information about an account, its activity, and its XRP balance. All information retrieved is relative to a particular version of the ledger. </p><h4>Request Format</h4><p>An example of an account_info request:</p><div id="code-3" class="multicode"><ul class="codetabs"><li><a class="current" href="#code-3-0">WebSocket</a></li><li><a href="#code-3-1">JSON-RPC</a></li><li><a href="#code-3-2">Commandline</a></li></ul>
 
 <div id="code-3-0"><pre><code title="Double-click to expand/collapse">{
   "id": 2,
@@ -637,7 +635,7 @@ rippled -- account_info r9cZA1mLK5R5Am25ArfXFmqgNwjZgnfk59 true</code></pre></di
 <tr>
 <td>account_data.index</td>
 <td>String</td>
-<td>(Deprecated) Data on another deterministic wallet that can be derived from the account’s secret. (Not widely supported; this feature may be dropped in the future.)</td>
+<td>A unique index for the AccountRoot node that represents this account in the ledger.</td>
 </tr>
 <tr>
 <td>ledger_current_index</td>
@@ -652,10 +650,10 @@ rippled -- account_info r9cZA1mLK5R5Am25ArfXFmqgNwjZgnfk59 true</code></pre></di
 <tr>
 <td>validated</td>
 <td>Boolean</td>
-<td>(<a href="https://ripplelabs.atlassian.net/browse/RIPD-275">Upcoming</a>) True if this data is from a validated ledger version; if omitted or set to false, this data is not final.</td>
+<td>True if this data is from a validated ledger version; if omitted or set to false, this data is not final. (<a href="https://ripplelabs.atlassian.net/browse/RIPD-275">New in version 0.26</a>)</td>
 </tr>
 </tbody>
-</table><h2 id="account-lines">account_lines</h2><p>The <code title="Double-click to expand/collapse">account_lines</code> method returns information about the account’s lines of trust, including balances in all non-XRP currencies and assets. All information retrieved is relative to a particular version of the ledger.</p><h4>Request Format</h4><p>An example of the request format:</p><div id="code-5" class="multicode"><ul class="codetabs"><li><a class="current" href="#code-5-0">WebSocket</a></li><li><a href="#code-5-1">JSON-RPC</a></li></ul>
+</table><h2 id="account-lines">account_lines</h2><p><a href="https://github.com/ripple/rippled/blob/master/src/ripple/module/rpc/handlers/AccountLines.cpp" title="Source">[Source]<br></a></p><p>The <code title="Double-click to expand/collapse">account_lines</code> method returns information about the account’s lines of trust, including balances in all non-XRP currencies and assets. All information retrieved is relative to a particular version of the ledger.</p><h4>Request Format</h4><p>An example of the request format:</p><div id="code-5" class="multicode"><ul class="codetabs"><li><a class="current" href="#code-5-0">WebSocket</a></li><li><a href="#code-5-1">JSON-RPC</a></li></ul>
 
 <div id="code-5-0"><pre><code title="Double-click to expand/collapse">{
   "id": 1,
@@ -703,8 +701,18 @@ rippled -- account_info r9cZA1mLK5R5Am25ArfXFmqgNwjZgnfk59 true</code></pre></di
 <td>String</td>
 <td>(Optional) A unique ID for a second account. If provided, show only lines of trust connecting the two accounts.</td>
 </tr>
+<tr>
+<td>limit</td>
+<td>Integer</td>
+<td>(<a href="https://ripplelabs.atlassian.net/browse/RIPD-343">Upcoming</a>, Optional, default varies) Limit the number of transactions to retrieve. The server is not required to honor this value.</td>
+</tr>
+<tr>
+<td>marker</td>
+<td>(Not Specified)</td>
+<td>(<a href="https://ripplelabs.atlassian.net/browse/RIPD-343">Upcoming</a>) Server-provided value to specify where to resume retrieving data from.</td>
+</tr>
 </tbody>
-</table><p>The following parameters are deprecated and may be removed without further notice: <code title="Double-click to expand/collapse">ledger</code> and <code title="Double-click to expand/collapse">peer_index</code>.</p><p>This method may be changed in the future to provide better scalability. See <a href="https://ripplelabs.atlassian.net/browse/RIPD-343">RIPD-343</a> for details and status.</p><h4>Response Format</h4><p>An example of a successful response:</p><div id="code-6" class="multicode"><ul class="codetabs"><li><a class="current" href="#code-6-0">WebSocket</a></li><li><a href="#code-6-1">JSON-RPC</a></li></ul>
+</table><p>The following parameters are deprecated and may be removed without further notice: <code title="Double-click to expand/collapse">ledger</code> and <code title="Double-click to expand/collapse">peer_index</code>.</p><h4>Response Format</h4><p>An example of a successful response:</p><div id="code-6" class="multicode"><ul class="codetabs"><li><a class="current" href="#code-6-0">WebSocket</a></li><li><a href="#code-6-1">JSON-RPC</a></li></ul>
 
 <div id="code-6-0"><pre><code title="Double-click to expand/collapse">{
     "id": 1,
@@ -1008,6 +1016,11 @@ rippled -- account_info r9cZA1mLK5R5Am25ArfXFmqgNwjZgnfk59 true</code></pre></di
 <td>Array</td>
 <td>Array of trust-line objects, as described below.</td>
 </tr>
+<tr>
+<td>marker</td>
+<td>(Not Specified)</td>
+<td>(<a href="https://ripplelabs.atlassian.net/browse/RIPD-343">Upcoming</a>) Server-defined value. Pass this to the next call in order to resume where this call left off.</td>
+</tr>
 </tbody>
 </table><p>Each trust-line object has some combination of the following fields, although not necessarily all of them:</p><table>
 <thead>
@@ -1064,7 +1077,7 @@ rippled -- account_info r9cZA1mLK5R5Am25ArfXFmqgNwjZgnfk59 true</code></pre></di
 <td>Ratio for outgoing <a href="https://ripple.com/wiki/Transit_Fees">transit fees</a> represented in billionths. (For example, a value of 500 million represents a 0.5:1 ratio.) As a special case, 0 is treated as a 1:1 ratio.</td>
 </tr>
 </tbody>
-</table><h2 id="account-offers">account_offers</h2><p>The <code title="Double-click to expand/collapse">account_offers</code> method retrieves a list of offers made by a given account that are outstanding as of a particular ledger version.</p><h4>Request Format</h4><p>An example of the request format:</p><div id="code-7" class="multicode"><ul class="codetabs"><li><a class="current" href="#code-7-0">WebSocket</a></li><li><a href="#code-7-1">JSON-RPC</a></li><li><a href="#code-7-2">Commandline</a></li></ul>
+</table><h2 id="account-offers">account_offers</h2><p><a href="https://github.com/ripple/rippled/blob/master/src/ripple/module/rpc/handlers/AccountOffers.cpp" title="Source">[Source]<br></a></p><p>The <code title="Double-click to expand/collapse">account_offers</code> method retrieves a list of offers made by a given account that are outstanding as of a particular ledger version.</p><h4>Request Format</h4><p>An example of the request format:</p><div id="code-7" class="multicode"><ul class="codetabs"><li><a class="current" href="#code-7-0">WebSocket</a></li><li><a href="#code-7-1">JSON-RPC</a></li><li><a href="#code-7-2">Commandline</a></li></ul>
 
 <div id="code-7-0"><pre><code title="Double-click to expand/collapse">{
   "id": 2,
@@ -1116,8 +1129,18 @@ rippled -- account_offers r9cZA1mLK5R5Am25ArfXFmqgNwjZgnfk59 current</code></pre
 <td>(Optional) Unsigned integer, or String</td>
 <td>(Optional, defaults to <code title="Double-click to expand/collapse">current</code>) The sequence number of the ledger to use, or “current”, “closed”, or “validated” to select a ledger dynamically. (See Ledger Indexes.)</td>
 </tr>
+<tr>
+<td>limit</td>
+<td>Integer</td>
+<td>(<a href="https://ripplelabs.atlassian.net/browse/RIPD-344">Upcoming</a>, Optional, default varies) Limit the number of transactions to retrieve. The server is not required to honor this value.</td>
+</tr>
+<tr>
+<td>marker</td>
+<td>(Not Specified)</td>
+<td>(<a href="https://ripplelabs.atlassian.net/browse/RIPD-344">Upcoming</a>) Server-provided value to specify where to resume retrieving data from.</td>
+</tr>
 </tbody>
-</table><p>The following parameter is deprecated and may be removed without further notice: <code title="Double-click to expand/collapse">ledger</code>.</p><p><em>Note:</em> This method may be changed in the future to support better scalability. See <a href="https://ripplelabs.atlassian.net/browse/RIPD-344">RIPD-344</a> for details and status.</p><h4>Response Format</h4><p>An example of a successful response:</p><div id="code-8" class="multicode"><ul class="codetabs"><li><a class="current" href="#code-8-0">WebSocket</a></li><li><a href="#code-8-1">JSON-RPC</a></li></ul>
+</table><p>The following parameter is deprecated and may be removed without further notice: <code title="Double-click to expand/collapse">ledger</code>.</p><h4>Response Format</h4><p>An example of a successful response:</p><div id="code-8" class="multicode"><ul class="codetabs"><li><a class="current" href="#code-8-0">WebSocket</a></li><li><a href="#code-8-1">JSON-RPC</a></li></ul>
 
 <div id="code-8-0"><pre><code title="Double-click to expand/collapse">{
   "id": 2,
@@ -1170,6 +1193,11 @@ Response:
 <td>Array</td>
 <td>Array of objects, where each object represents an offer made by this account that is outstanding as of the requested ledger version.</td>
 </tr>
+<tr>
+<td>marker</td>
+<td>(Not Specified)</td>
+<td>(<a href="https://ripplelabs.atlassian.net/browse/RIPD-344">Upcoming</a>) Server-defined value. Pass this to the next call in order to resume where this call left off.</td>
+</tr>
 </tbody>
 </table><p>Each offer object contains the following fields:</p><table>
 <thead>
@@ -1201,7 +1229,7 @@ Response:
 <td>The amount the account accepting the offer provides, as a String representing an amount in XRP, or a currency specification object. (See <a href="#specifying-currency-amounts">Specifying Currency Amounts</a>)</td>
 </tr>
 </tbody>
-</table><h2 id="account-tx">account_tx</h2><p>The <code title="Double-click to expand/collapse">account_tx</code> method retrieves a list of transactions that involved the specified account.</p><h4>Request Format</h4><p>An example of the request format:</p><div id="code-9" class="multicode"><ul class="codetabs"><li><a class="current" href="#code-9-0">WebSocket</a></li><li><a href="#code-9-1">JSON-RPC</a></li><li><a href="#code-9-2">Commandline</a></li></ul>
+</table><h2 id="account-tx">account_tx</h2><p><a href="https://github.com/ripple/rippled/blob/master/src/ripple/module/rpc/handlers/AccountTx.cpp" title="Source">[Source]<br></a></p><p>The <code title="Double-click to expand/collapse">account_tx</code> method retrieves a list of transactions that involved the specified account.</p><h4>Request Format</h4><p>An example of the request format:</p><div id="code-9" class="multicode"><ul class="codetabs"><li><a class="current" href="#code-9-0">WebSocket</a></li><li><a href="#code-9-1">JSON-RPC</a></li><li><a href="#code-9-2">Commandline</a></li></ul>
 
 <div id="code-9-0"><pre><code title="Double-click to expand/collapse">{
   "id": 2,
@@ -1293,7 +1321,8 @@ rippled -- account_tx r9cZA1mLK5R5Am25ArfXFmqgNwjZgnfk59 -1 -1 2 false false fal
 <td>Server-provided value to specify where to resume retrieving data from.</td>
 </tr>
 </tbody>
-</table><p>There is also a deprecated legacy variation of the <code title="Double-click to expand/collapse">account_tx</code> method. For that reason, we recommend <em>not using any of the following fields</em>: <code title="Double-click to expand/collapse">offset</code>, <code title="Double-click to expand/collapse">count</code>, <code title="Double-click to expand/collapse">descending</code>, <code title="Double-click to expand/collapse">ledger_max</code>, <code title="Double-click to expand/collapse">ledger_min</code></p><h5>Iterating over queried data</h5><p>If you want to retrieve an amount of data that is higher than the server’s maximum <code title="Double-click to expand/collapse">limit</code> value, or you want to break up your request into multiple smaller requests, you can use the <code title="Double-click to expand/collapse">marker</code> field to pick up in the same place you left off. For each subsequent request, pass the <code title="Double-click to expand/collapse">marker</code> value from the previous request to instruct rippled to resume from the point where you left off.</p><p>However, in the time between requests, things may change so that <code title="Double-click to expand/collapse">"ledger_index_min": -1</code> and <code title="Double-click to expand/collapse">"ledger_index_max": -1</code> may refer to different ledger versions than they did before. To make sure you iterate over the same exact data set, take the <code title="Double-click to expand/collapse">ledger_index_min</code> and <code title="Double-click to expand/collapse">ledger_index_max</code> values provided in the first response, and use those values for all subsequent requests. </p><h4>Response Format</h4><p>An example of a successful response:</p><div id="code-10" class="multicode"><ul class="codetabs"><li><a class="current" href="#code-10-0">WebSocket</a></li><li><a href="#code-10-1">JSON-RPC</a></li></ul>
+</table><p><a href="https://github.com/ripple/rippled/blob/master/src/ripple/module/rpc/handlers/AccountTxSwitch.cpp" title="Source">[Source]<br></a>
+There is also a deprecated legacy variation of the <code title="Double-click to expand/collapse">account_tx</code> method. For that reason, we recommend <em>not using any of the following fields</em>: <code title="Double-click to expand/collapse">offset</code>, <code title="Double-click to expand/collapse">count</code>, <code title="Double-click to expand/collapse">descending</code>, <code title="Double-click to expand/collapse">ledger_max</code>, <code title="Double-click to expand/collapse">ledger_min</code>.</p><h5>Iterating over queried data</h5><p>If you want to retrieve an amount of data that is higher than the server’s maximum <code title="Double-click to expand/collapse">limit</code> value, or you want to break up your request into multiple smaller requests, you can use the <code title="Double-click to expand/collapse">marker</code> field to pick up in the same place you left off. For each subsequent request, pass the <code title="Double-click to expand/collapse">marker</code> value from the previous request to instruct rippled to resume from the point where you left off.</p><p>However, in the time between requests, things may change so that <code title="Double-click to expand/collapse">"ledger_index_min": -1</code> and <code title="Double-click to expand/collapse">"ledger_index_max": -1</code> may refer to different ledger versions than they did before. To make sure you iterate over the same exact data set, take the <code title="Double-click to expand/collapse">ledger_index_min</code> and <code title="Double-click to expand/collapse">ledger_index_max</code> values provided in the first response, and use those values for all subsequent requests. </p><h4>Response Format</h4><p>An example of a successful response:</p><div id="code-10" class="multicode"><ul class="codetabs"><li><a class="current" href="#code-10-0">WebSocket</a></li><li><a href="#code-10-1">JSON-RPC</a></li></ul>
 
 <div id="code-10-0"><pre><code title="Double-click to expand/collapse">{
     "id": 2,
@@ -1846,7 +1875,7 @@ rippled -- account_tx r9cZA1mLK5R5Am25ArfXFmqgNwjZgnfk59 -1 -1 2 false false fal
 <td>Whether or not the transaction is included in a validated ledger. Any transaction not yet in a validated ledger is subject to change.</td>
 </tr>
 </tbody>
-</table><h2 id="wallet-propose">wallet_propose</h2><p>Use the <code title="Double-click to expand/collapse">wallet_propose</code> method to generate the keys needed for a new account. The account created this way will only become officially included in the Ripple network when it receives a transaction that provides enough XRP to meet the account reserve. (The <code title="Double-click to expand/collapse">wallet_propose</code> command does not affect the global network. Technically, it is not strictly necessary for creating a new account: you could generate keys some other way, but that is not recommended.)</p><p><em>The <code title="Double-click to expand/collapse">wallet_propose</code> request is an admin command that cannot be run by unpriviledged users!</em> (Since admin commands are not transmitted over the outside network this command is protected against people sniffing the network for account secrets.)</p><h4>Request Format</h4><p>An example of the request format:</p><div id="code-11" class="multicode"><ul class="codetabs"><li><a class="current" href="#code-11-0">WebSocket</a></li><li><a href="#code-11-1">JSON-RPC</a></li><li><a href="#code-11-2">Commandline</a></li></ul>
+</table><h2 id="wallet-propose">wallet_propose</h2><p><a href="https://github.com/ripple/rippled/blob/master/src/ripple/module/rpc/handlers/WalletPropose.cpp" title="Source">[Source]<br></a></p><p>Use the <code title="Double-click to expand/collapse">wallet_propose</code> method to generate the keys needed for a new account. The account created this way will only become officially included in the Ripple network when it receives a transaction that provides enough XRP to meet the account reserve. (The <code title="Double-click to expand/collapse">wallet_propose</code> command does not affect the global network. Technically, it is not strictly necessary for creating a new account: you could generate keys some other way, but that is not recommended.)</p><p><em>The <code title="Double-click to expand/collapse">wallet_propose</code> request is an admin command that cannot be run by unpriviledged users!</em> (Since admin commands are not transmitted over the outside network this command is protected against people sniffing the network for account secrets.)</p><h4>Request Format</h4><p>An example of the request format:</p><div id="code-11" class="multicode"><ul class="codetabs"><li><a class="current" href="#code-11-0">WebSocket</a></li><li><a href="#code-11-1">JSON-RPC</a></li><li><a href="#code-11-2">Commandline</a></li></ul>
 
 <div id="code-11-0"><pre><code title="Double-click to expand/collapse">{
     "command": "wallet_propose",
@@ -1935,7 +1964,7 @@ rippled -- wallet_propose test</code></pre></div>
 <td>The public key of the account, in hex format.</td>
 </tr>
 </tbody>
-</table><p>The key generated by this method can also be used as a regular key for an account if you use the <a href="https://ripple.com/wiki/index.php/API_Example_Transactions#Set_Regular_Key">SetRegularKey transaction type</a> to do so.</p><h1 id="managing-ledgers">Managing Ledgers</h1><p>The globally-shared ledger is the core of the Ripple Network. Each <code title="Double-click to expand/collapse">rippled</code> server keeps a current version of the ledger, which contains all the accounts, transactions, offers, and other data in the network in an optimized tree format. As transactions and offers are proposed, each server incorporates them into its current copy of the ledger, closes it periodically, and (if configured) participates in the process of advancing the globally-validated version. After concensus is reached in the network, that ledger version is validated and becomes permanently immutable. Any transactions that were not included in one ledger become candidates to be included in the next validated version.</p><h2 id="ledger">ledger</h2><p>Retrieve information about the public ledger.</p><h4>Request Format</h4><p>An example of the request format:</p><div id="code-13" class="multicode"><ul class="codetabs"><li><a class="current" href="#code-13-0">WebSocket</a></li><li><a href="#code-13-1">JSON-RPC</a></li><li><a href="#code-13-2">Commandline</a></li></ul>
+</table><p>The key generated by this method can also be used as a regular key for an account if you use the <a href="https://ripple.com/wiki/index.php/API_Example_Transactions#Set_Regular_Key">SetRegularKey transaction type</a> to do so.</p><h1 id="managing-ledgers">Managing Ledgers</h1><p>The globally-shared ledger is the core of the Ripple Network. Each <code title="Double-click to expand/collapse">rippled</code> server keeps a current version of the ledger, which contains all the accounts, transactions, offers, and other data in the network in an optimized tree format. As transactions and offers are proposed, each server incorporates them into its current copy of the ledger, closes it periodically, and (if configured) participates in the process of advancing the globally-validated version. After concensus is reached in the network, that ledger version is validated and becomes permanently immutable. Any transactions that were not included in one ledger become candidates to be included in the next validated version.</p><h2 id="ledger">ledger</h2><p><a href="https://github.com/ripple/rippled/blob/master/src/ripple/module/rpc/handlers/Ledger.cpp" title="Source">[Source]<br></a></p><p>Retrieve information about the public ledger.</p><h4>Request Format</h4><p>An example of the request format:</p><div id="code-13" class="multicode"><ul class="codetabs"><li><a class="current" href="#code-13-0">WebSocket</a></li><li><a href="#code-13-1">JSON-RPC</a></li><li><a href="#code-13-2">Commandline</a></li></ul>
 
 <div id="code-13-0"><pre><code title="Double-click to expand/collapse">{
     "command": "ledger",
@@ -2106,8 +2135,13 @@ rippled -- ledger current false</code></pre></div>
 <td>String</td>
 <td>Hash of the transaction information included in this ledger, as hex</td>
 </tr>
+<tr>
+<td>validated</td>
+<td>Boolean</td>
+<td>(<a href="https://ripplelabs.atlassian.net/browse/RIPD-569">Upcoming</a>) If included and set to <code title="Double-click to expand/collapse">true</code>, the information in this request describes a validated ledger version. Otherwise, the information is subject to change.</td>
+</tr>
 </tbody>
-</table><p>The following fields are deprecated and may be removed without further notice: <code title="Double-click to expand/collapse">hash</code>, <code title="Double-click to expand/collapse">seqNum</code>, <code title="Double-click to expand/collapse">totalCoins</code>.</p><h2 id="ledger-closed">ledger_closed</h2><p>The <code title="Double-click to expand/collapse">ledger_closed</code> method returns the unique identifiers of the most recently closed ledger. (This ledger is not necessarily validated and immutable yet.)</p><h4>Request Format</h4><p>An example of the request format:</p><div id="code-15" class="multicode"><ul class="codetabs"><li><a class="current" href="#code-15-0">WebSocket</a></li><li><a href="#code-15-1">JSON-RPC</a></li><li><a href="#code-15-2">Commandline</a></li></ul>
+</table><p>The following fields are deprecated and may be removed without further notice: <code title="Double-click to expand/collapse">hash</code>, <code title="Double-click to expand/collapse">seqNum</code>, <code title="Double-click to expand/collapse">totalCoins</code>.</p><h2 id="ledger-closed">ledger_closed</h2><p><a href="https://github.com/ripple/rippled/blob/master/src/ripple/module/rpc/handlers/LedgerClosed.cpp" title="Source">[Source]<br></a></p><p>The <code title="Double-click to expand/collapse">ledger_closed</code> method returns the unique identifiers of the most recently closed ledger. (This ledger is not necessarily validated and immutable yet.)</p><h4>Request Format</h4><p>An example of the request format:</p><div id="code-15" class="multicode"><ul class="codetabs"><li><a class="current" href="#code-15-0">WebSocket</a></li><li><a href="#code-15-1">JSON-RPC</a></li><li><a href="#code-15-2">Commandline</a></li></ul>
 
 <div id="code-15-0"><pre><code title="Double-click to expand/collapse">{
    "id": 2,
@@ -2166,7 +2200,7 @@ rippled -- ledger_closed</code></pre></div>
 <td>Sequence number of this ledger</td>
 </tr>
 </tbody>
-</table><h2 id="ledger-current">ledger_current</h2><p>The <code title="Double-click to expand/collapse">ledger_current</code> method returns the unique identifiers of the current in-progress ledger. This command is mostly useful for testing, because the ledger returned is still in flux.</p><h4>Request Format</h4><p>An example of the request format:</p><div id="code-17" class="multicode"><ul class="codetabs"><li><a class="current" href="#code-17-0">WebSocket</a></li><li><a href="#code-17-1">JSON-RPC</a></li><li><a href="#code-17-2">Commandline</a></li></ul>
+</table><h2 id="ledger-current">ledger_current</h2><p><a href="https://github.com/ripple/rippled/blob/master/src/ripple/module/rpc/handlers/LedgerCurrent.cpp" title="Source">[Source]<br></a></p><p>The <code title="Double-click to expand/collapse">ledger_current</code> method returns the unique identifiers of the current in-progress ledger. This command is mostly useful for testing, because the ledger returned is still in flux.</p><h4>Request Format</h4><p>An example of the request format:</p><div id="code-17" class="multicode"><ul class="codetabs"><li><a class="current" href="#code-17-0">WebSocket</a></li><li><a href="#code-17-1">JSON-RPC</a></li><li><a href="#code-17-2">Commandline</a></li></ul>
 
 <div id="code-17-0"><pre><code title="Double-click to expand/collapse">{
    "id": 2,
@@ -2218,7 +2252,7 @@ rippled -- ledger_current</code></pre></div>
 <td>Sequence number of this ledger</td>
 </tr>
 </tbody>
-</table><p>A <code title="Double-click to expand/collapse">ledger_hash</code> field is not provided, because the hash of the current ledger is constantly changing along with its contents.</p><h2 id="ledger-data">ledger_data</h2><p>The <code title="Double-click to expand/collapse">ledger_data</code> method retrieves contents of the specified ledger. You can iterate through several calls in order to retrieve the entire contents of a single ledger version.</p><h4>Request Format</h4><p>An example of the request format:</p><div id="code-19" class="multicode"><ul class="codetabs"><li><a class="current" href="#code-19-0">WebSocket</a></li><li><a href="#code-19-1">JSON-RPC</a></li></ul>
+</table><p>A <code title="Double-click to expand/collapse">ledger_hash</code> field is not provided, because the hash of the current ledger is constantly changing along with its contents.</p><h2 id="ledger-data">ledger_data</h2><p><a href="https://github.com/ripple/rippled/blob/master/src/ripple/module/rpc/handlers/LedgerData.cpp" title="Source">[Source]<br></a></p><p>The <code title="Double-click to expand/collapse">ledger_data</code> method retrieves contents of the specified ledger. You can iterate through several calls in order to retrieve the entire contents of a single ledger version.</p><h4>Request Format</h4><p>An example of the request format:</p><div id="code-19" class="multicode"><ul class="codetabs"><li><a class="current" href="#code-19-0">WebSocket</a></li><li><a href="#code-19-1">JSON-RPC</a></li></ul>
 
 <div id="code-19-0"><pre><code title="Double-click to expand/collapse">{
    "id": 2,
@@ -2502,7 +2536,7 @@ rippled -- ledger_current</code></pre></div>
 <td>Unique identifier for this ledger entry, as hex.</td>
 </tr>
 </tbody>
-</table><h2 id="ledger-entry">ledger_entry</h2><p>The <code title="Double-click to expand/collapse">ledger_entry</code> method returns a single entry from the specified ledger. See <a href="https://ripple.com/wiki/Ledger_Format#Entries">LedgerEntryType</a> for information on the different types of objects you can retrieve. <em>Note:</em> There is no commandline version of this method. You can use the <a href="#json"><code title="Double-click to expand/collapse">json</code></a> command to access this method from the commandline instead.</p><h4>Request Format</h4><p>An example of the request format:</p><div id="code-21" class="multicode"><ul class="codetabs"><li><a class="current" href="#code-21-0">WebSocket</a></li><li><a href="#code-21-1">JSON-RPC</a></li></ul>
+</table><h2 id="ledger-entry">ledger_entry</h2><p><a href="https://github.com/ripple/rippled/blob/master/src/ripple/module/rpc/handlers/LedgerEntry.cpp" title="Source">[Source]<br></a></p><p>The <code title="Double-click to expand/collapse">ledger_entry</code> method returns a single entry from the specified ledger. See <a href="https://ripple.com/wiki/Ledger_Format#Entries">LedgerEntryType</a> for information on the different types of objects you can retrieve. <em>Note:</em> There is no commandline version of this method. You can use the <a href="#json"><code title="Double-click to expand/collapse">json</code></a> command to access this method from the commandline instead.</p><h4>Request Format</h4><p>An example of the request format:</p><div id="code-21" class="multicode"><ul class="codetabs"><li><a class="current" href="#code-21-0">WebSocket</a></li><li><a href="#code-21-1">JSON-RPC</a></li></ul>
 
 <div id="code-21-0"><pre><code title="Double-click to expand/collapse">{
   "id": 3,
@@ -2525,7 +2559,7 @@ rippled -- ledger_current</code></pre></div>
 }</code></pre></div>
 </div><p><a class="button" href="ripple-api-tool.html#ledger_entry">Try it!</a></p><p>This method can retrieve several different types of data. You can select which type of item to retrieve by passing the appropriate parameters. Specifically, you should provide exactly one of the following fields:</p><ol>
 <li><code title="Double-click to expand/collapse">index</code> - Retrieve an individual ledger entry by its unique index</li>
-<li><code title="Double-click to expand/collapse">account_root</code> - Retrieve an account node, similar to the <a class="active" href="#account-info">account_info</a> command</li>
+<li><code title="Double-click to expand/collapse">account_root</code> - Retrieve an account node, similar to the <a href="#account-info">account_info</a> command</li>
 <li><code title="Double-click to expand/collapse">directory</code> - Retrieve a directory node, which contains a list of IDs linking things</li>
 <li><code title="Double-click to expand/collapse">offer</code> - Retrieve an offer node, which defines an offer to exchange currency</li>
 <li><code title="Double-click to expand/collapse">ripple_state</code> - Retrieve a RippleState node, which defines currency (IOU) balances and credit limits between accounts</li>
@@ -2678,7 +2712,7 @@ rippled -- ledger_current</code></pre></div>
 <td>(<code title="Double-click to expand/collapse">"binary":true</code> only) Binary data of the ledger node retrieved, as hex.</td>
 </tr>
 </tbody>
-</table><h1 id="managing-transactions">Managing Transactions</h1><p>Transactions are the only thing that can modify the shared global ledger of the Ripple Network. All business on the Ripple Network takes the form of transactions, which include not only payments, but also currency-exchange offers, account settings, and changes to the properties of the network itself (like adopting new features).</p><p>There are several sources of complication in transactions. Unlike traditional banking, where a trusted third party (the bank, or the <a href="http://en.wikipedia.org/wiki/Automated_Clearing_House">ACH</a>) verifies the participants’ identities and ensures their balances are adjusted accurately, Ripple uses cryptography and decentralized computing power to accomplish the same thing. Sending XRP, the Ripple Network’s native crypto-currency, requires no third party aside from the distributed network itself. However, that is missing out on the key feature of Ripple: unlike individual crypto-currencies, the Ripple Network natively supports balances in any currency. This brings far more power, but it also means that the system must account for <a href="http://en.wikipedia.org/wiki/Counterparty_risk#Counterparty_risk">counterparty risk</a>, currency conversions, and other issues. The Ripple Network must be robust to keep track of which transactions have been completely validated, even when subject to hardware failures, attacks, or natural disasters.</p><h2 id="tx">tx</h2><p>The <code title="Double-click to expand/collapse">tx</code> method retrieves information on a single transaction. </p><h4>Request Format</h4><p>An example of the request format:</p><div id="code-23" class="multicode"><ul class="codetabs"><li><a class="current" href="#code-23-0">WebSocket</a></li><li><a href="#code-23-1">JSON-RPC</a></li><li><a href="#code-23-2">Commandline</a></li></ul>
+</table><h1 id="managing-transactions">Managing Transactions</h1><p>Transactions are the only thing that can modify the shared global ledger of the Ripple Network. All business on the Ripple Network takes the form of transactions, which include not only payments, but also currency-exchange offers, account settings, and changes to the properties of the network itself (like adopting new features).</p><p>There are several sources of complication in transactions. Unlike traditional banking, where a trusted third party (the bank, or the <a href="http://en.wikipedia.org/wiki/Automated_Clearing_House">ACH</a>) verifies the participants’ identities and ensures their balances are adjusted accurately, Ripple uses cryptography and decentralized computing power to accomplish the same thing. Sending XRP, the Ripple Network’s native crypto-currency, requires no third party aside from the distributed network itself. However, that is missing out on the key feature of Ripple: unlike individual crypto-currencies, the Ripple Network natively supports balances in any currency. This brings far more power, but it also means that the system must account for <a href="http://en.wikipedia.org/wiki/Counterparty_risk#Counterparty_risk">counterparty risk</a>, currency conversions, and other issues. The Ripple Network must be robust to keep track of which transactions have been completely validated, even when subject to hardware failures, attacks, or natural disasters.</p><h2 id="tx">tx</h2><p><a href="https://github.com/ripple/rippled/blob/master/src/ripple/module/rpc/handlers/Tx.cpp" title="Source">[Source]<br></a></p><p>The <code title="Double-click to expand/collapse">tx</code> method retrieves information on a single transaction. </p><h4>Request Format</h4><p>An example of the request format:</p><div id="code-23" class="multicode"><ul class="codetabs"><li><a class="current" href="#code-23-0">WebSocket</a></li><li><a href="#code-23-1">JSON-RPC</a></li><li><a href="#code-23-2">Commandline</a></li></ul>
 
 <div id="code-23-0"><pre><code title="Double-click to expand/collapse">{
   "id": 1,
@@ -2884,7 +2918,7 @@ tx E08D6E9754025BA2534A78707605E0601F03ACE063687A0CA1BDDACFCD1698C7 false</code>
 <td>Other fields from the <a href="https://ripple.com/wiki/Transaction_Format">Transaction object</a></td>
 </tr>
 </tbody>
-</table><p><em>Note:</em> If the transaction was not found, it means that the rippled server could not find it from the ledger versions on hand. However, that does not mean that the transaction does not exist; it may simply have been included in an older ledger version that the <code title="Double-click to expand/collapse">rippled</code> does not have on hand anymore.</p><h2 id="transaction-entry">transaction_entry</h2><p>The <code title="Double-click to expand/collapse">transaction_entry</code> method retrieves information on a single transaction from a specific ledger version. (The <a href="#tx"><code title="Double-click to expand/collapse">tx</code></a> command, by contrast, searches all ledgers for the specified transaction. We recommend using that method instead.) </p><h4>Request Format</h4><p>An example of the request format:</p><div id="code-25" class="multicode"><ul class="codetabs"><li><a class="current" href="#code-25-0">WebSocket</a></li><li><a href="#code-25-1">JSON-RPC</a></li><li><a href="#code-25-2">Commandline</a></li></ul>
+</table><p><em>Note:</em> If the transaction was not found, it means that the rippled server could not find it from the ledger versions on hand. However, that does not mean that the transaction does not exist; it may simply have been included in an older ledger version that the <code title="Double-click to expand/collapse">rippled</code> does not have on hand anymore.</p><h2 id="transaction-entry">transaction_entry</h2><p><a href="https://github.com/ripple/rippled/blob/master/src/ripple/module/rpc/handlers/TransactionEntry.cpp" title="Source">[Source]<br></a></p><p>The <code title="Double-click to expand/collapse">transaction_entry</code> method retrieves information on a single transaction from a specific ledger version. (The <a href="#tx"><code title="Double-click to expand/collapse">tx</code></a> command, by contrast, searches all ledgers for the specified transaction. We recommend using that method instead.) </p><h4>Request Format</h4><p>An example of the request format:</p><div id="code-25" class="multicode"><ul class="codetabs"><li><a class="current" href="#code-25-0">WebSocket</a></li><li><a href="#code-25-1">JSON-RPC</a></li><li><a href="#code-25-2">Commandline</a></li></ul>
 
 <div id="code-25-0"><pre><code title="Double-click to expand/collapse">{
   "id": 4,
@@ -3091,7 +3125,7 @@ rippled -- transaction_entry E08D6E9754025BA2534A78707605E0601F03ACE063687A0CA1B
 <li>The transaction just does not exist</li>
 <li>The transaction exists, but not in the specified ledger version</li>
 <li>The server does not have the specified ledger version available. Another server that has the correct version on hand may have a different response.</li>
-</ul><h2 id="tx-history">tx_history</h2><p>The <code title="Double-click to expand/collapse">tx_history</code> method retrieves a selection of the most recent transactions made.</p><p><em>Caution:</em> This method is deprecated, and may be removed without further notice.</p><h4>Request Format</h4><p>An example of the request format:</p><div id="code-27" class="multicode"><ul class="codetabs"><li><a class="current" href="#code-27-0">WebSocket</a></li><li><a href="#code-27-1">JSON-RPC</a></li><li><a href="#code-27-2">Commandline</a></li></ul>
+</ul><h2 id="tx-history">tx_history</h2><p><a href="https://github.com/ripple/rippled/blob/master/src/ripple/module/rpc/handlers/TxHistory.cpp" title="Source">[Source]<br></a></p><p>The <code title="Double-click to expand/collapse">tx_history</code> method retrieves a selection of the most recent transactions made.</p><p><em>Caution:</em> This method is deprecated, and may be removed without further notice.</p><h4>Request Format</h4><p>An example of the request format:</p><div id="code-27" class="multicode"><ul class="codetabs"><li><a class="current" href="#code-27-0">WebSocket</a></li><li><a href="#code-27-1">JSON-RPC</a></li><li><a href="#code-27-2">Commandline</a></li></ul>
 
 <div id="code-27-0"><pre><code title="Double-click to expand/collapse">{
   "id": 5,
@@ -3961,11 +3995,11 @@ rippled -- tx_history 0</code></pre></div>
 <td>Array of transaction objects.</td>
 </tr>
 </tbody>
-</table><p>The fields included in each transaction object vary slightly depending on the type of transaction. See <a href="https://ripple.com/wiki/Transaction_Format">Transaction Format</a> for details.</p><h2 id="path-find">path_find</h2><p><em>WebSocket API only!</em> The <code title="Double-click to expand/collapse">path_find</code> method searches for a path along which a transaction can possibly be made, and periodically sends updates when the path changes over time. For a simpler version that is supported by JSON-RPC, see <a href="#ripple-path-find"><code title="Double-click to expand/collapse">ripple_path_find</code></a>. For payments occurring strictly in XRP, it is not necessary to find a path, because XRP can be sent directly to any account. </p><p>There are three different modes, or sub-commands, of the path_find command. Specify which one you want with the <code title="Double-click to expand/collapse">subcommand</code> parameter:</p><ul>
+</table><p>The fields included in each transaction object vary slightly depending on the type of transaction. See <a href="https://ripple.com/wiki/Transaction_Format">Transaction Format</a> for details.</p><h2 id="path-find">path_find</h2><p><a href="https://github.com/ripple/rippled/blob/master/src/ripple/module/rpc/handlers/PathFind.cpp" title="Source">[Source]<br></a></p><p><em>WebSocket API only!</em> The <code title="Double-click to expand/collapse">path_find</code> method searches for a path along which a transaction can possibly be made, and periodically sends updates when the path changes over time. For a simpler version that is supported by JSON-RPC, see <a href="#ripple-path-find"><code title="Double-click to expand/collapse">ripple_path_find</code></a>. For payments occurring strictly in XRP, it is not necessary to find a path, because XRP can be sent directly to any account. </p><p>There are three different modes, or sub-commands, of the path_find command. Specify which one you want with the <code title="Double-click to expand/collapse">subcommand</code> parameter:</p><ul>
 <li><code title="Double-click to expand/collapse">create</code> - Start sending pathfinding information </li>
 <li><code title="Double-click to expand/collapse">close</code> - Stop sending pathfinding information</li>
 <li><code title="Double-click to expand/collapse">status</code> - Get the information of the currently-open pathfinding request</li>
-</ul><p>Although the <code title="Double-click to expand/collapse">rippled</code> server attempts to find the cheapest path or combination of paths for making a payment, it is not guaranteed that the paths returned by this method are, in fact, the best paths. Due to server load, pathfinding may not find the best results. Additionally, you should be careful with the pathfinding results from untrusted servers. A server could be modified to return less-than-optimal paths in order to earn money for its operators. If you do not have your own server that you can trust with pathfinding, you should compare the results of pathfinding from multiple servers operated by different parties, to minimize the risk of a single server returning poor results. (<em>Note:</em> A server returning less-than-optimal results is not necessarily proof of malicious behavior; it could also be a symptom of heavy server load.)</p><h3 id="path-find-create">path_find create</h3><p>The <code title="Double-click to expand/collapse">create</code> subcommand of <code title="Double-click to expand/collapse">path_find</code> creates an ongoing request to find possible paths along which a payment transaction could be made from one specified account such that another account receives a desired amount of some currency. The initial response contains a suggested path between the two addresses that would result in the desired amount being received. After that, the server sends additional messages, with <code title="Double-click to expand/collapse">"type": "path_find"</code>, with updates to the potential paths. The frequency of updates is left to the discretion of the server, but it usually means once every few seconds when there is a new ledger version.</p><p>A client can only have one pathfinding request open at a time. If another pathfinding request is already open on the same connection, the old request is automatically closed and replaced with the new request.</p><h4>Request Format</h4><p>An example of the request format:</p><div id="code-29" class="multicode"><ul class="codetabs"><li><a class="current" href="#code-29-0">WebSocket</a></li></ul>
+</ul><p>Although the <code title="Double-click to expand/collapse">rippled</code> server attempts to find the cheapest path or combination of paths for making a payment, it is not guaranteed that the paths returned by this method are, in fact, the best paths. Due to server load, pathfinding may not find the best results. Additionally, you should be careful with the pathfinding results from untrusted servers. A server could be modified to return less-than-optimal paths in order to earn money for its operators. If you do not have your own server that you can trust with pathfinding, you should compare the results of pathfinding from multiple servers operated by different parties, to minimize the risk of a single server returning poor results. (<em>Note:</em> A server returning less-than-optimal results is not necessarily proof of malicious behavior; it could also be a symptom of heavy server load.)</p><h3 id="path-find-create">path_find create</h3><p><a href="https://github.com/ripple/rippled/blob/master/src/ripple/module/rpc/handlers/PathFind.cpp#L38" title="Source">[Source]<br></a></p><p>The <code title="Double-click to expand/collapse">create</code> subcommand of <code title="Double-click to expand/collapse">path_find</code> creates an ongoing request to find possible paths along which a payment transaction could be made from one specified account such that another account receives a desired amount of some currency. The initial response contains a suggested path between the two addresses that would result in the desired amount being received. After that, the server sends additional messages, with <code title="Double-click to expand/collapse">"type": "path_find"</code>, with updates to the potential paths. The frequency of updates is left to the discretion of the server, but it usually means once every few seconds when there is a new ledger version.</p><p>A client can only have one pathfinding request open at a time. If another pathfinding request is already open on the same connection, the old request is automatically closed and replaced with the new request.</p><h4>Request Format</h4><p>An example of the request format:</p><div id="code-29" class="multicode"><ul class="codetabs"><li><a class="current" href="#code-29-0">WebSocket</a></li></ul>
 
 <div id="code-29-0"><pre><code title="Double-click to expand/collapse">{
     "id": 8,
@@ -5272,7 +5306,7 @@ rippled -- tx_history 0</code></pre></div>
     },
     "source_account": "r9cZA1mLK5R5Am25ArfXFmqgNwjZgnfk59"
 }</code></pre></div>
-</div><h3 id="path-find-close">path_find close</h3><p>The <code title="Double-click to expand/collapse">close</code> subcommand of <code title="Double-click to expand/collapse">path_find</code> instructs the server to stop sending information about the current open pathfinding request.</p><h4>Request Format</h4><p>An example of the request format:</p><div id="code-32" class="multicode"><ul class="codetabs"><li><a class="current" href="#code-32-0">WebSocket</a></li></ul>
+</div><h3 id="path-find-close">path_find close</h3><p><a href="https://github.com/ripple/rippled/blob/master/src/ripple/module/rpc/handlers/PathFind.cpp#L46" title="Source">[Source]<br></a></p><p>The <code title="Double-click to expand/collapse">close</code> subcommand of <code title="Double-click to expand/collapse">path_find</code> instructs the server to stop sending information about the current open pathfinding request.</p><h4>Request Format</h4><p>An example of the request format:</p><div id="code-32" class="multicode"><ul class="codetabs"><li><a class="current" href="#code-32-0">WebSocket</a></li></ul>
 
 <div id="code-32-0"><pre><code title="Double-click to expand/collapse">{
   "id": 57,
@@ -5294,7 +5328,7 @@ rippled -- tx_history 0</code></pre></div>
 <td>Use <code title="Double-click to expand/collapse">"close"</code> to send the close subcommand</td>
 </tr>
 </tbody>
-</table><h4>Response Format</h4><p>If a pathfinding request was successfully closed, the response follows the same format as the initial response to <a href="#path_find-create"><code title="Double-click to expand/collapse">path_find create</code></a>. If there was no outstanding pathfinding request, an error is returned instead.</p><h3 id="path-find-status">path_find status</h3><p>The <code title="Double-click to expand/collapse">status</code> subcommand of <code title="Double-click to expand/collapse">path_find</code> requests an immediate update about the client’s currently-open pathfinding request.</p><h4>Request Format</h4><p>An example of the request format:</p><div id="code-33" class="multicode"><ul class="codetabs"><li><a class="current" href="#code-33-0">WebSocket</a></li></ul>
+</table><h4>Response Format</h4><p>If a pathfinding request was successfully closed, the response follows the same format as the initial response to <a href="#path_find-create"><code title="Double-click to expand/collapse">path_find create</code></a>. If there was no outstanding pathfinding request, an error is returned instead.</p><h3 id="path-find-status">path_find status</h3><p><a href="https://github.com/ripple/rippled/blob/master/src/ripple/module/rpc/handlers/PathFind.cpp#L57" title="Source">[Source]<br></a></p><p>The <code title="Double-click to expand/collapse">status</code> subcommand of <code title="Double-click to expand/collapse">path_find</code> requests an immediate update about the client’s currently-open pathfinding request.</p><h4>Request Format</h4><p>An example of the request format:</p><div id="code-33" class="multicode"><ul class="codetabs"><li><a class="current" href="#code-33-0">WebSocket</a></li></ul>
 
 <div id="code-33-0"><pre><code title="Double-click to expand/collapse">{
   "id": 58,
@@ -5316,7 +5350,7 @@ rippled -- tx_history 0</code></pre></div>
 <td>Use <code title="Double-click to expand/collapse">"status"</code> to send the status subcommand</td>
 </tr>
 </tbody>
-</table><h4>Response Format</h4><p>If a pathfinding request is open, the response follows the same format as the initial response to <a href="#path_find-create"><code title="Double-click to expand/collapse">path_find create</code></a>. If there was no outstanding pathfinding request, an error is returned instead. (Prior to version 0.26, the server erroneously reports success. See <a href="https://ripplelabs.atlassian.net/browse/RIPD-293">RIPD-293</a> for more information.)</p><h2 id="ripple-path-find">ripple_path_find</h2><p>The <code title="Double-click to expand/collapse">ripple_path_find</code> method is a simplified version of <a href="#path-find"><code title="Double-click to expand/collapse">path_find</code></a> that provides a single response to be used to make a payment transaction immediately. It is available in both the WebSocket and JSON-RPC APIs. However, the results tend to become outdated as time passes. Instead of making many subsequent calls, you should use <a href="#path-find"><code title="Double-click to expand/collapse">path_find</code></a> instead where possible.</p><p>Although the <code title="Double-click to expand/collapse">rippled</code> server attempts to find the cheapest path or combination of paths for making a payment, it is not guaranteed that the paths returned by this method are, in fact, the best paths. Due to server load, pathfinding may not find the best results. Additionally, you should be careful with the pathfinding results from untrusted servers. A server could be modified to return less-than-optimal paths in order to earn money for its operators. If you do not have your own server that you can trust with pathfinding, you should compare the results of pathfinding from multiple servers operated by different parties, to minimize the risk of a single server returning poor results. (<em>Note:</em> A server returning less-than-optimal results is not necessarily proof of malicious behavior; it could also be a symptom of heavy server load.)</p><h4>Request Format</h4><p>An example of the request format:</p><div id="code-34" class="multicode"><ul class="codetabs"><li><a class="current" href="#code-34-0">WebSocket</a></li><li><a href="#code-34-1">JSON-RPC</a></li><li><a href="#code-34-2">Commandline</a></li></ul>
+</table><h4>Response Format</h4><p>If a pathfinding request is open, the response follows the same format as the initial response to <a href="#path_find-create"><code title="Double-click to expand/collapse">path_find create</code></a>. If there was no outstanding pathfinding request, an error is returned instead. (Prior to version 0.26, the server erroneously reports success. See <a href="https://ripplelabs.atlassian.net/browse/RIPD-293">RIPD-293</a> for more information.)</p><h2 id="ripple-path-find">ripple_path_find</h2><p><a href="https://github.com/ripple/rippled/blob/master/src/ripple/module/rpc/handlers/RipplePathFind.cpp" title="Source">[Source]<br></a></p><p>The <code title="Double-click to expand/collapse">ripple_path_find</code> method is a simplified version of <a href="#path-find"><code title="Double-click to expand/collapse">path_find</code></a> that provides a single response to be used to make a payment transaction immediately. It is available in both the WebSocket and JSON-RPC APIs. However, the results tend to become outdated as time passes. Instead of making many subsequent calls, you should use <a href="#path-find"><code title="Double-click to expand/collapse">path_find</code></a> instead where possible.</p><p>Although the <code title="Double-click to expand/collapse">rippled</code> server attempts to find the cheapest path or combination of paths for making a payment, it is not guaranteed that the paths returned by this method are, in fact, the best paths. Due to server load, pathfinding may not find the best results. Additionally, you should be careful with the pathfinding results from untrusted servers. A server could be modified to return less-than-optimal paths in order to earn money for its operators. If you do not have your own server that you can trust with pathfinding, you should compare the results of pathfinding from multiple servers operated by different parties, to minimize the risk of a single server returning poor results. (<em>Note:</em> A server returning less-than-optimal results is not necessarily proof of malicious behavior; it could also be a symptom of heavy server load.)</p><h4>Request Format</h4><p>An example of the request format:</p><div id="code-34" class="multicode"><ul class="codetabs"><li><a class="current" href="#code-34-0">WebSocket</a></li><li><a href="#code-34-1">JSON-RPC</a></li><li><a href="#code-34-2">Commandline</a></li></ul>
 
 <div id="code-34-0"><pre><code title="Double-click to expand/collapse">{
     "id": 8,
@@ -5661,7 +5695,7 @@ rippled -- ripple_path_find '{"source_account": "r9cZA1mLK5R5Am25ArfXFmqgNwjZgnf
 <td><a href="#specifying-currency-amounts">Currency amount</a> that the source would have to send along this path in order for the destination to receive the desired amount</td>
 </tr>
 </tbody>
-</table><p>The following fields are deprecated, and may be omitted: <code title="Double-click to expand/collapse">paths_canonical</code>, and <code title="Double-click to expand/collapse">paths_expanded</code>. If they appear, you should disregard them.</p><h2 id="sign">sign</h2><p>The <code title="Double-click to expand/collapse">sign</code> method takes a transaction, specified as JSON, and a secret key, and returns a signed binary representation of the transaction that can be submitted. The result is always different, even when you provide the same transaction and secret key.</p><p><em>Note:</em> It is possible and preferable to sign a transaction without connecting to a server instead of using this command. For example, <a href="https://github.com/ripple/ripple-lib/blob/develop/bin/rsign.js">ripple-lib’s rsign.js</a> demonstrates offline signing of a transaction. You should prefer to do offline signing of a transaction, especially when do not control the server you are sending a transaction to. An untrustworthy server can abuse its position to change the transaction before signing it, or worse, use your secret to sign additional arbitrary transactions as if they came from you.</p><h4>Request Format</h4><p>An example of the request format:</p><div id="code-36" class="multicode"><ul class="codetabs"><li><a class="current" href="#code-36-0">WebSocket</a></li><li><a href="#code-36-1">JSON-RPC</a></li><li><a href="#code-36-2">Commandline</a></li></ul>
+</table><p>The following fields are deprecated, and may be omitted: <code title="Double-click to expand/collapse">paths_canonical</code>, and <code title="Double-click to expand/collapse">paths_expanded</code>. If they appear, you should disregard them.</p><h2 id="sign">sign</h2><p><a href="https://github.com/ripple/rippled/blob/master/src/ripple/module/rpc/handlers/Sign.cpp" title="Source">[Source]<br></a></p><p>The <code title="Double-click to expand/collapse">sign</code> method takes a transaction, specified as JSON, and a secret key, and returns a signed binary representation of the transaction that can be submitted. The result is always different, even when you provide the same transaction and secret key.</p><p><em>Note:</em> It is possible and preferable to sign a transaction without connecting to a server instead of using this command. For example, <a href="https://github.com/ripple/ripple-lib/blob/develop/bin/rsign.js">ripple-lib’s rsign.js</a> demonstrates offline signing of a transaction. You should prefer to do offline signing of a transaction, especially when do not control the server you are sending a transaction to. An untrustworthy server can abuse its position to change the transaction before signing it, or worse, use your secret to sign additional arbitrary transactions as if they came from you.</p><h4>Request Format</h4><p>An example of the request format:</p><div id="code-36" class="multicode"><ul class="codetabs"><li><a class="current" href="#code-36-0">WebSocket</a></li><li><a href="#code-36-1">JSON-RPC</a></li><li><a href="#code-36-2">Commandline</a></li></ul>
 
 <div id="code-36-0"><pre><code title="Double-click to expand/collapse">{
   "id": 2,
@@ -5807,7 +5841,7 @@ rippled -- sign sssssssssssssssssssssssssssss '{"TransactionType": "Payment", "A
 <li>Do not write this error to a log file that can be seen by multiple people</li>
 <li>Do not paste this error to a public place for debugging</li>
 <li>Do not display the error message on a website, even by accident</li>
-</ul><h2 id="submit">submit</h2><p>The <code title="Double-click to expand/collapse">submit</code> method sends a transaction to the network to be confirmed and included in future ledgers. There are two ways to use it: either you can supply JSON along with your secret key (not recommended), or you can take a pre-signed transaction blob (for example, one created with <a href="#sign"><code title="Double-click to expand/collapse">sign</code></a>, or better yet, something <a href="https://github.com/ripple/ripple-lib/blob/develop/bin/rsign.js">signed offline</a>) and submit it as-is.</p><h4>Request Format</h4><p>An example of the request format:</p><div id="code-38" class="multicode"><ul class="codetabs"><li><a class="current" href="#code-38-0">WebSocket</a></li><li><a href="#code-38-1">JSON-RPC</a></li><li><a href="#code-38-2">Commandline</a></li></ul>
+</ul><h2 id="submit">submit</h2><p><a href="https://github.com/ripple/rippled/blob/master/src/ripple/module/rpc/handlers/Submit.cpp" title="Source">[Source]<br></a></p><p>The <code title="Double-click to expand/collapse">submit</code> method sends a transaction to the network to be confirmed and included in future ledgers. There are two ways to use it: either you can supply JSON along with your secret key (not recommended), or you can take a pre-signed transaction blob (for example, one created with <a href="#sign"><code title="Double-click to expand/collapse">sign</code></a>, or better yet, something <a href="https://github.com/ripple/ripple-lib/blob/develop/bin/rsign.js">signed offline</a>) and submit it as-is.</p><h4>Request Format</h4><p>An example of the request format:</p><div id="code-38" class="multicode"><ul class="codetabs"><li><a class="current" href="#code-38-0">WebSocket</a></li><li><a href="#code-38-1">JSON-RPC</a></li><li><a href="#code-38-2">Commandline</a></li></ul>
 
 <div id="code-38-0"><pre><code title="Double-click to expand/collapse">{
   "id": 2,
@@ -5968,7 +6002,7 @@ submit sssssssssssssssssssssssssssss '{"TransactionType":"Payment", "Account":"r
 <li>Do not write this error to a log file that can be seen by multiple people</li>
 <li>Do not paste this error to a public place for debugging</li>
 <li>Do not display the error message on a website, even by accident</li>
-</ul><h2 id="book-offers">book_offers</h2><p>The <code title="Double-click to expand/collapse">book_offers</code> method retrieves a list of offers, also known as the <a href="http://www.investopedia.com/terms/o/order-book.asp">order book</a>, between two currencies. If the results are very large, a partial result is returned with a marker so that subsequent requests can resume from where the previous one left off.</p><h4>Request Format</h4><p>An example of the request format:</p><div id="code-40" class="multicode"><ul class="codetabs"><li><a class="current" href="#code-40-0">WebSocket</a></li><li><a href="#code-40-1">JSON-RPC</a></li><li><a href="#code-40-2">Commandline</a></li></ul>
+</ul><h2 id="book-offers">book_offers</h2><p><a href="https://github.com/ripple/rippled/blob/master/src/ripple/module/rpc/handlers/BookOffers.cpp" title="Source">[Source]<br></a></p><p>The <code title="Double-click to expand/collapse">book_offers</code> method retrieves a list of offers, also known as the <a href="http://www.investopedia.com/terms/o/order-book.asp">order book</a>, between two currencies. If the results are very large, a partial result is returned with a marker so that subsequent requests can resume from where the previous one left off.</p><h4>Request Format</h4><p>An example of the request format:</p><div id="code-40" class="multicode"><ul class="codetabs"><li><a class="current" href="#code-40-0">WebSocket</a></li><li><a href="#code-40-1">JSON-RPC</a></li><li><a href="#code-40-2">Commandline</a></li></ul>
 
 <div id="code-40-0"><pre><code title="Double-click to expand/collapse">{
   "id": 4,
@@ -6159,7 +6193,7 @@ rippled -- book_offers 'USD/rvYAfWj5gh67oV6fW32ZzP3Aw4Eubs59B' 'EUR/rvYAfWj5gh67
 <td>The exchange rate, as the ratio <code title="Double-click to expand/collapse">taker_pays</code> divided by <code title="Double-click to expand/collapse">taker_gets</code>. For fairness, offers that have the same quality are automatically taken first-in, first-out. (In other words, if multiple people offer to exchange currency at the same rate, the oldest offer is taken first.)</td>
 </tr>
 </tbody>
-</table><h1 id="subscriptions">Subscriptions</h1><p>Using subscriptions, you can have the server push updates to your client when various events happen, so that you can know right away and react accordingly. Subscriptions are only supported in the WebSocket API, where you can receive additional responses in the same channel.</p><p>JSON-RPC support for subscription callbacks is deprecated and may not work as expected.</p><h2 id="subscribe">subscribe</h2><p>The <code title="Double-click to expand/collapse">subscribe</code> method requests periodic notifications from the server when certain events happen. </p><h4>Request Format</h4><p>An example of the request format:</p><div id="code-42" class="multicode"><ul class="codetabs"><li><a class="current" href="#code-42-0">WebSocket - accounts</a></li><li><a href="#code-42-1">WebSocket - offer book</a></li></ul>
+</table><h1 id="subscriptions">Subscriptions</h1><p>Using subscriptions, you can have the server push updates to your client when various events happen, so that you can know right away and react accordingly. Subscriptions are only supported in the WebSocket API, where you can receive additional responses in the same channel.</p><p>JSON-RPC support for subscription callbacks is deprecated and may not work as expected.</p><h2 id="subscribe">subscribe</h2><p><a href="https://github.com/ripple/rippled/blob/master/src/ripple/module/rpc/handlers/Subscribe.cpp" title="Source">[Source]<br></a></p><p>The <code title="Double-click to expand/collapse">subscribe</code> method requests periodic notifications from the server when certain events happen. </p><h4>Request Format</h4><p>An example of the request format:</p><div id="code-42" class="multicode"><ul class="codetabs"><li><a class="current" href="#code-42-0">WebSocket - accounts</a></li><li><a href="#code-42-1">WebSocket - offer book</a></li></ul>
 
 <div id="code-42-0"><pre><code title="Double-click to expand/collapse">{
   "id": "Example watch Bitstamp's hot wallet",
@@ -6512,7 +6546,7 @@ rippled -- book_offers 'USD/rvYAfWj5gh67oV6fW32ZzP3Aw4Eubs59B' 'EUR/rvYAfWj5gh67
 <td>If true, this transaction is included in a validated ledger. Responses from the <code title="Double-click to expand/collapse">transaction</code> stream should always be validated.</td>
 </tr>
 </tbody>
-</table><h2 id="unsubscribe">unsubscribe</h2><p>The <code title="Double-click to expand/collapse">unsubscribe</code> command tells the server to stop sending messages for a particular subscription or set of subscriptions.</p><h4>Request Format</h4><p>An example of the request format:</p><div id="code-44" class="multicode"><ul class="codetabs"><li><a class="current" href="#code-44-0">WebSocket</a></li></ul>
+</table><h2 id="unsubscribe">unsubscribe</h2><p><a href="https://github.com/ripple/rippled/blob/master/src/ripple/module/rpc/handlers/Unsubscribe.cpp" title="Source">[Source]<br></a></p><p>The <code title="Double-click to expand/collapse">unsubscribe</code> command tells the server to stop sending messages for a particular subscription or set of subscriptions.</p><h4>Request Format</h4><p>An example of the request format:</p><div id="code-44" class="multicode"><ul class="codetabs"><li><a class="current" href="#code-44-0">WebSocket</a></li></ul>
 
 <div id="code-44-0"><pre><code title="Double-click to expand/collapse">{
     "id": "Unsubscribe a lot of stuff",
@@ -6596,7 +6630,7 @@ rippled -- book_offers 'USD/rvYAfWj5gh67oV6fW32ZzP3Aw4Eubs59B' 'EUR/rvYAfWj5gh67
     "status": "success",
     "type": "response"
 }</code></pre></div>
-</div><p>The response follows the <a href="#response-formatting">standard format</a>, with a successful result containing no fields.</p><h1 id="server-information">Server Information</h1><p>There are also commands that retrieve information about the current state of the server. These may be useful for monitoring the health of the server, or in preparing for making other API methods. For example, you may query for the current fee schedule before sending a transaction, or you may check which ledger versions are available before digging into the ledger history for a specific record.</p><h2 id="server-info">server_info</h2><p>The <code title="Double-click to expand/collapse">server_info</code> command asks the server for a human-readable version of various information about the <code title="Double-click to expand/collapse">rippled</code> server being queried.</p><h4>Request Format</h4><p>An example of the request format:</p><div id="code-46" class="multicode"><ul class="codetabs"><li><a class="current" href="#code-46-0">WebSocket</a></li><li><a href="#code-46-1">JSON-RPC</a></li></ul>
+</div><p>The response follows the <a href="#response-formatting">standard format</a>, with a successful result containing no fields.</p><h1 id="server-information">Server Information</h1><p>There are also commands that retrieve information about the current state of the server. These may be useful for monitoring the health of the server, or in preparing for making other API methods. For example, you may query for the current fee schedule before sending a transaction, or you may check which ledger versions are available before digging into the ledger history for a specific record.</p><h2 id="server-info">server_info</h2><p><a href="https://github.com/ripple/rippled/blob/master/src/ripple/module/rpc/handlers/ServerInfo.cpp" title="Source">[Source]<br></a></p><p>The <code title="Double-click to expand/collapse">server_info</code> command asks the server for a human-readable version of various information about the <code title="Double-click to expand/collapse">rippled</code> server being queried.</p><h4>Request Format</h4><p>An example of the request format:</p><div id="code-46" class="multicode"><ul class="codetabs"><li><a class="current" href="#code-46-0">WebSocket</a></li><li><a href="#code-46-1">JSON-RPC</a></li></ul>
 
 <div id="code-46-0"><pre><code title="Double-click to expand/collapse">{
   "id": 11,
@@ -6788,7 +6822,7 @@ rippled -- book_offers 'USD/rvYAfWj5gh67oV6fW32ZzP3Aw4Eubs59B' 'EUR/rvYAfWj5gh67
 <td>Minimum number of trusted validations required in order to validate a ledger version. Some circumstances may cause the server to require more validations.</td>
 </tr>
 </tbody>
-</table><h2 id="server-state">server_state</h2><p>The <code title="Double-click to expand/collapse">server_state</code> command asks the server for various machine-readable information about the <code title="Double-click to expand/collapse">rippled</code> server’s current state. The results are very similar to <a href="#server-info"><code title="Double-click to expand/collapse">server_info</code></a>, but generally the units are chosen to be easier to process instead of easier to read. (For example, XRP values are given in integer drops instead of scientific notation or decimal values, and time is given in milliseconds instead of seconds.)</p><h4>Request Format</h4><p>An example of the request format:</p><div id="code-48" class="multicode"><ul class="codetabs"><li><a class="current" href="#code-48-0">WebSocket</a></li><li><a href="#code-48-1">JSON-RPC</a></li></ul>
+</table><h2 id="server-state">server_state</h2><p><a href="https://github.com/ripple/rippled/blob/master/src/ripple/module/rpc/handlers/ServerState.cpp" title="Source">[Source]<br></a></p><p>The <code title="Double-click to expand/collapse">server_state</code> command asks the server for various machine-readable information about the <code title="Double-click to expand/collapse">rippled</code> server’s current state. The results are very similar to <a href="#server-info"><code title="Double-click to expand/collapse">server_info</code></a>, but generally the units are chosen to be easier to process instead of easier to read. (For example, XRP values are given in integer drops instead of scientific notation or decimal values, and time is given in milliseconds instead of seconds.)</p><h4>Request Format</h4><p>An example of the request format:</p><div id="code-48" class="multicode"><ul class="codetabs"><li><a class="current" href="#code-48-0">WebSocket</a></li><li><a href="#code-48-1">JSON-RPC</a></li></ul>
 
 <div id="code-48-0"><pre><code title="Double-click to expand/collapse">{
   "id": 12,
@@ -6977,7 +7011,7 @@ rippled -- book_offers 'USD/rvYAfWj5gh67oV6fW32ZzP3Aw4Eubs59B' 'EUR/rvYAfWj5gh67
 <td>Minimum number of trusted validations required in order to validate a ledger version. Some circumstances may cause the server to require more validations.</td>
 </tr>
 </tbody>
-</table><h1 id="convenience-functions">Convenience Functions</h1><p>The rippled server also provides a few simple commands purely for convenience.</p><h2 id="ping">ping</h2><p>The <code title="Double-click to expand/collapse">ping</code> command returns an acknowledgement, so that clients can test the connection status and latency.</p><h4>Request Format</h4><p>An example of the request format:</p><div id="code-50" class="multicode"><ul class="codetabs"><li><a class="current" href="#code-50-0">WebSocket</a></li><li><a href="#code-50-1">JSON-RPC</a></li><li><a href="#code-50-2">Commandline</a></li></ul>
+</table><h1 id="convenience-functions">Convenience Functions</h1><p>The rippled server also provides a few simple commands purely for convenience.</p><h2 id="ping">ping</h2><p><a href="https://github.com/ripple/rippled/blob/master/src/ripple/module/rpc/handlers/Ping.cpp" title="Source">[Source]<br></a></p><p>The <code title="Double-click to expand/collapse">ping</code> command returns an acknowledgement, so that clients can test the connection status and latency.</p><h4>Request Format</h4><p>An example of the request format:</p><div id="code-50" class="multicode"><ul class="codetabs"><li><a class="current" href="#code-50-0">WebSocket</a></li><li><a href="#code-50-1">JSON-RPC</a></li><li><a href="#code-50-2">Commandline</a></li></ul>
 
 <div id="code-50-0"><pre><code title="Double-click to expand/collapse">{
     "id": 1,
@@ -7011,7 +7045,7 @@ rippled -- ping</code></pre></div>
         "status": "success"
     }
 }</code></pre></div>
-</div><p>The response follows the <a href="#response-formatting">standard format</a>, with a successful result containing no fields. The client can measure the round-trip time from request to response as latency.</p><h2 id="random">random</h2><p>The <code title="Double-click to expand/collapse">random</code> command provides a random number to be used as a source of entropy for random number generation by clients.</p><h4>Request Format</h4><p>An example of the request format:</p><div id="code-52" class="multicode"><ul class="codetabs"><li><a class="current" href="#code-52-0">WebSocket</a></li><li><a href="#code-52-1">JSON-RPC</a></li><li><a href="#code-52-2">Commandline</a></li></ul>
+</div><p>The response follows the <a href="#response-formatting">standard format</a>, with a successful result containing no fields. The client can measure the round-trip time from request to response as latency.</p><h2 id="random">random</h2><p><a href="https://github.com/ripple/rippled/blob/master/src/ripple/module/rpc/handlers/Random.cpp" title="Source">[Source]<br></a></p><p>The <code title="Double-click to expand/collapse">random</code> command provides a random number to be used as a source of entropy for random number generation by clients.</p><h4>Request Format</h4><p>An example of the request format:</p><div id="code-52" class="multicode"><ul class="codetabs"><li><a class="current" href="#code-52-0">WebSocket</a></li><li><a href="#code-52-1">JSON-RPC</a></li><li><a href="#code-52-2">Commandline</a></li></ul>
 
 <div id="code-52-0"><pre><code title="Double-click to expand/collapse">{
     "id": 1,
@@ -7077,6 +7111,8 @@ rippled -q -- json ledger_closed '{}'</code></pre></div>
    }
 }</code></pre></div>
 </div><p>The response follows the <a href="#response-formatting">standard format</a>, with whichever fields are appropriate to the type of command made.</p>
+    
+    
     </div>
   </div>
 <div class="footer">
diff --git a/websocket_api.md b/websocket_api.md
index a1cb5db231..193a422d68 100644
--- a/websocket_api.md
+++ b/websocket_api.md
@@ -582,7 +582,7 @@ The request accepts the following paramters:
 | ledger_index | String or Unsigned Integer| (Optional) The sequence number of the ledger to use, or a shortcut string to choose a ledger automatically. (See [Specifying a Ledger](#specifying-a-ledger-instance))|
 | peer | String | (Optional) A unique ID for a second account. If provided, show only lines of trust connecting the two accounts. |
 | limit | Integer | ([Upcoming](https://ripplelabs.atlassian.net/browse/RIPD-343), Optional, default varies) Limit the number of transactions to retrieve. The server is not required to honor this value. |
-| marker | (Not Specified) | [Upcoming](https://ripplelabs.atlassian.net/browse/RIPD-343) Server-provided value to specify where to resume retrieving data from. |
+| marker | (Not Specified) | ([Upcoming](https://ripplelabs.atlassian.net/browse/RIPD-343)) Server-provided value to specify where to resume retrieving data from. |
 
 The following parameters are deprecated and may be removed without further notice: `ledger` and `peer_index`.
 
@@ -886,6 +886,7 @@ The response follows the [standard format](#response-formatting), with a success
 |-------|------|-------------|
 | account | String | Unique address of the account this request corresponds to |
 | lines | Array | Array of trust-line objects, as described below. |
+| marker | (Not Specified) | ([Upcoming](https://ripplelabs.atlassian.net/browse/RIPD-343)) Server-defined value. Pass this to the next call in order to resume where this call left off. |
 
 Each trust-line object has some combination of the following fields, although not necessarily all of them:
 
@@ -901,6 +902,7 @@ Each trust-line object has some combination of the following fields, although no
 | quality_in | Unsigned Integer | Ratio for incoming [transit fees](https://ripple.com/wiki/Transit_Fees) represented in billionths. (For example, a value of 500 million represents a 0.5:1 ratio.) As a special case, 0 is treated as a 1:1 ratio. |
 | quality_out | Unsigned Integer | Ratio for outgoing [transit fees](https://ripple.com/wiki/Transit_Fees) represented in billionths. (For example, a value of 500 million represents a 0.5:1 ratio.) As a special case, 0 is treated as a 1:1 ratio. |
 
+
 ## account_offers ##
 [[Source]<br>](https://github.com/ripple/rippled/blob/master/src/ripple/module/rpc/handlers/AccountOffers.cpp "Source")
 
@@ -951,8 +953,8 @@ A request can include the following parameters:
 | ledger | Unsigned integer, or String | (Deprecated, Optional) A unique identifier for the ledger version to use, such as a ledger sequence number, a hash, or a shortcut such as "validated". |
 | ledger_hash | String | (Optional) A 20-byte hex string identifying the ledger version to use. |
 | ledger_index | (Optional) Unsigned integer, or String | (Optional, defaults to `current`) The sequence number of the ledger to use, or "current", "closed", or "validated" to select a ledger dynamically. (See Ledger Indexes.) |
-| limit | Integer | ([Upcoming](https://ripplelabs.atlassian.net/browse/RIPD-343), Optional, default varies) Limit the number of transactions to retrieve. The server is not required to honor this value. |
-| marker | (Not Specified) | ([Upcoming](https://ripplelabs.atlassian.net/browse/RIPD-343)) Server-provided value to specify where to resume retrieving data from. |
+| limit | Integer | ([Upcoming](https://ripplelabs.atlassian.net/browse/RIPD-344), Optional, default varies) Limit the number of transactions to retrieve. The server is not required to honor this value. |
+| marker | (Not Specified) | ([Upcoming](https://ripplelabs.atlassian.net/browse/RIPD-344)) Server-provided value to specify where to resume retrieving data from. |
 
 The following parameter is deprecated and may be removed without further notice: `ledger`.
 
@@ -1006,6 +1008,8 @@ The response follows the [standard format](#response-formatting), with a success
 |-------|------|-------------|
 | account | String | Unique address identifying the account that made the offers |
 | offers | Array | Array of objects, where each object represents an offer made by this account that is outstanding as of the requested ledger version. |
+| marker | (Not Specified) | ([Upcoming](https://ripplelabs.atlassian.net/browse/RIPD-344)) Server-defined value. Pass this to the next call in order to resume where this call left off. |
+
 
 Each offer object contains the following fields:
 
@@ -1806,6 +1810,7 @@ The response follows the [standard format](#response-formatting), with a success
 | parent_hash | String | Unique identifying hash of the ledger that came immediately before this one. |
 | total_coins | String | Total number of XRP drops in the network, as a quoted integer. (This decreases as transaction fees cause XRP to be destroyed.) |
 | transaction_hash | String | Hash of the transaction information included in this ledger, as hex |
+| validated | Boolean | ([Upcoming](https://ripplelabs.atlassian.net/browse/RIPD-569)) If included and set to `true`, the information in this request describes a validated ledger version. Otherwise, the information is subject to change. |
 
 The following fields are deprecated and may be removed without further notice: `hash`, `seqNum`, `totalCoins`.