[DOC] update ripple-rest doc and api tool

- add transaction-fee
- fix generate wallet
- fix /account/{account}/payments
- fix /transactions

js/apitool-rest.js

@@ -65,11 +65,11 @@ var DEFAULT_ADDRESS_1 = "rf1BiGeXwwQoi8Z2ueFYTEXSwuJYfV2Jpn";
 var DEFAULT_ADDRESS_2 = "ra5nK24KXen9AHvsdFTKHSANinZseWnPcX";
 var DEFAULT_HASH = "9D591B18EDDD34F0B6CF4223A2940AEA2C3CC778925BABF289E0011CD8FA056E";
 
-Request('Generate Account', {
+Request('Generate Wallet', {
     method: GET,
-    path: "/v1/accounts/new",
-    description: 'Generate the keys for a potential new account',
-    link: '#generate-account'
+    path: "/v1/wallet/new",
+    description: 'Randomly generate keys for a potential new Ripple account',
+    link: '#generate-wallet'
 });
 
 Request('Get Account Balances', {
@@ -129,7 +129,7 @@ Request('Prepare Payment', {
 
 Request('Submit Payment', {
     method: POST,
-    path: '/v1/payments',
+    path: '/v1/accounts/{:source_address}/payments',
     description: 'Send a prepared payment to the network.',
     link: '#submit-payment',
     test_only: true,
@@ -157,6 +157,9 @@ Request('Submit Payment', {
           "partial_payment": false,
           "no_direct_ripple": false
         }
+    },
+    params: {
+        "{:source_address}": DEFAULT_ADDRESS_1
     }
 });
 
@@ -240,7 +243,7 @@ Request("Get Server Status", {
 
 Request("Retrieve Ripple Transaction", {
     method: GET,
-    path: "/v1/tx/{:hash}",
+    path: "/v1/transactions/{:hash}",
     description: "Retrieve a raw Ripple transaction",
     link: "#retrieve-ripple-transaction",
     params: {
@@ -248,6 +251,13 @@ Request("Retrieve Ripple Transaction", {
     }
 });
 
+Request("Retrieve Transaction Fee", {
+    method: GET,
+    path: "/v1/transaction-fee",
+    description: "Retrieve the current transaction fee for the connected rippled server(s)",
+    link: "#retrieve-transaction-fee",
+});
+
 Request("Generate UUID", {
     method: GET,
     path: "/v1/uuid",

rest-api-tool.html

@@ -123,6 +123,7 @@ mixpanel.init("132d42885e094171f34467fc54da6fab");
         <li>Get Server Status</li>
         <br/>
         <li>Retrieve Ripple Transaction</li>
+        <li>Retrieve Transaction Fee</li>
         <li>Generate UUID</li>
       </ul>
       <div id='command_table'>

ripplerest_api.md

@@ -175,7 +175,7 @@ When errors occur, the server returns an HTTP status code in the 400-599 range,
 
 In general, the HTTP status code is indicative of where the problem occurred:
 
-* Codes in the 200-299 range indicate success. (*Note:* This behavior is new in [Ripple-REST v1.3.0](https://github.com/ripple/ripple-rest/releases/tag/v1.3.0-rc4). Previous versions sometimes return 200 OK for some types of errors.)
+* Codes in the 200-299 range indicate success. (*Note:* This behavior is new in [Ripple-REST v1.3.0](https://github.com/ripple/ripple-rest/releases/tag/1.3.0). Previous versions sometimes return 200 OK for some types of errors.)
     * Unless otherwise specified, methods are expected to return `200 OK` on success.
 * Codes in the 400-499 range indicate that the request was invalid or incorrect somehow. For example:
     * `400 Bad Request` occurs if the JSON body is malformed. This includes syntax errors as well as when invalid or mutually-exclusive options are selected.
@@ -331,7 +331,7 @@ Submitted transactions can have additional fields reflecting the current status
 
 ### Memo Objects ###
 
-(New in [Ripple-REST v1.3.0](https://github.com/ripple/ripple-rest/releases/tag/v1.3.0-rc4))
+(New in [Ripple-REST v1.3.0](https://github.com/ripple/ripple-rest/releases/tag/1.3.0))
 
 Memo objects represent arbitrary data that can be included in a transaction. The overall size of the `memos` field cannot exceed 1KB after serialization.
 
@@ -391,7 +391,7 @@ Accounts are the core unit of authentication in the Ripple Network. Each account
 
 ## Generate Wallet ##
 
-(New in [Ripple-REST v1.3.0](https://github.com/ripple/ripple-rest/releases/tag/v1.3.0-rc4))
+(New in [Ripple-REST v1.3.0](https://github.com/ripple/ripple-rest/releases/tag/1.3.0))
 
 Randomly generate keys for a potential new Ripple account.
 
@@ -1831,6 +1831,8 @@ The result is a JSON object, whose `transaction` field has the requested transac
 
 ## Retrieve Transaction Fee ##
 
+(New in [Ripple-REST v1.3.1](https://github.com/ripple/ripple-rest/releases/tag/1.3.1-rc1))
+
 Retrieve the current transaction fee for the rippled server `ripple-rest` is connected to. If `ripple-rest` is connected to multiple rippled servers, the median fee between the connected servers is calculated.
 
 <div class='multicode'>