Add link def snippets to admin methods and move websocket tool links

content/references/rippled-api/public-rippled-methods/account-methods/account_currencies.md

@@ -37,7 +37,7 @@ An example of the request format:
 
 <!-- MULTICODE_BLOCK_END -->
 
-[Try it! >](ripple-api-tool.html#account_currencies)
+[Try it! >](websocket-api-tool.html#account_currencies)
 
 The request includes the following parameters:
 

content/references/rippled-api/public-rippled-methods/account-methods/account_info.md

@@ -47,7 +47,7 @@ rippled account_info r9cZA1mLK5R5Am25ArfXFmqgNwjZgnfk59 true
 
 <!-- MULTICODE_BLOCK_END -->
 
-[Try it! >](ripple-api-tool.html#account_info)
+[Try it! >](websocket-api-tool.html#account_info)
 
 The request contains the following parameters:
 

content/references/rippled-api/public-rippled-methods/account-methods/account_lines.md

@@ -36,7 +36,7 @@ An example of the request format:
 
 <!-- MULTICODE_BLOCK_END -->
 
-[Try it! >](ripple-api-tool.html#account_lines)
+[Try it! >](websocket-api-tool.html#account_lines)
 
 The request accepts the following paramters:
 

content/references/rippled-api/public-rippled-methods/account-methods/account_offers.md

@@ -43,7 +43,7 @@ rippled account_offers r9cZA1mLK5R5Am25ArfXFmqgNwjZgnfk59 current
 
 <!-- MULTICODE_BLOCK_END -->
 
-[Try it! >](ripple-api-tool.html#account_offers)
+[Try it! >](websocket-api-tool.html#account_offers)
 
 A request can include the following parameters:
 

content/references/rippled-api/public-rippled-methods/account-methods/account_tx.md

@@ -51,7 +51,7 @@ rippled -- account_tx r9cZA1mLK5R5Am25ArfXFmqgNwjZgnfk59 -1 -1 2 5 1 0 1
 
 <!-- MULTICODE_BLOCK_END -->
 
-[Try it! >](ripple-api-tool.html#account_tx)
+[Try it! >](websocket-api-tool.html#account_tx)
 
 The request includes the following parameters:
 

content/references/rippled-api/public-rippled-methods/ledger-methods/ledger.md

@@ -52,7 +52,7 @@ rippled ledger current
 
 <!-- MULTICODE_BLOCK_END -->
 
-[Try it! >](ripple-api-tool.html#ledger)
+[Try it! >](websocket-api-tool.html#ledger)
 
 The request can contain the following parameters:
 

content/references/rippled-api/public-rippled-methods/ledger-methods/ledger_closed.md

@@ -37,7 +37,7 @@ rippled ledger_closed
 
 <!-- MULTICODE_BLOCK_END -->
 
-[Try it! >](ripple-api-tool.html#ledger_closed)
+[Try it! >](websocket-api-tool.html#ledger_closed)
 
 This method accepts no parameters.
 

content/references/rippled-api/public-rippled-methods/ledger-methods/ledger_current.md

@@ -38,7 +38,7 @@ rippled ledger_current
 
 <!-- MULTICODE_BLOCK_END -->
 
-[Try it! >](ripple-api-tool.html#ledger_current)
+[Try it! >](websocket-api-tool.html#ledger_current)
 
 The request contains no parameters.
 

content/references/rippled-api/public-rippled-methods/ledger-methods/ledger_entry.md

@@ -40,7 +40,7 @@ An example of the request format:
 
 <!-- MULTICODE_BLOCK_END -->
 
-[Try it! >](ripple-api-tool.html#ledger_entry)
+[Try it! >](websocket-api-tool.html#ledger_entry)
 
 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:
 

content/references/rippled-api/public-rippled-methods/path-and-order-book-methods/book_offers.md

@@ -56,7 +56,7 @@ rippled book_offers 'USD/rvYAfWj5gh67oV6fW32ZzP3Aw4Eubs59B' 'EUR/rvYAfWj5gh67oV6
 
 <!-- MULTICODE_BLOCK_END -->
 
-[Try it! >](ripple-api-tool.html#book_offers)
+[Try it! >](websocket-api-tool.html#book_offers)
 
 The request includes the following parameters:
 

content/references/rippled-api/public-rippled-methods/path-and-order-book-methods/path_find.md

@@ -42,7 +42,7 @@ An example of the request format:
 
 <!-- MULTICODE_BLOCK_END -->
 
-[Try it! >](ripple-api-tool.html#path_find)
+[Try it! >](websocket-api-tool.html#path_find)
 
 The request includes the following parameters:
 

content/references/rippled-api/public-rippled-methods/path-and-order-book-methods/ripple_path_find.md

@@ -72,7 +72,7 @@ rippled ripple_path_find '{"source_account": "r9cZA1mLK5R5Am25ArfXFmqgNwjZgnfk59
 
 <!-- MULTICODE_BLOCK_END -->
 
-[Try it! >](ripple-api-tool.html#ripple_path_find)
+[Try it! >](websocket-api-tool.html#ripple_path_find)
 
 The request includes the following parameters:
 

content/references/rippled-api/public-rippled-methods/server-info-methods/server_info.md

@@ -37,7 +37,7 @@ rippled server_info
 
 <!-- MULTICODE_BLOCK_END -->
 
-[Try it! >](ripple-api-tool.html#server_info)
+[Try it! >](websocket-api-tool.html#server_info)
 
 The request does not take any parameters.
 

content/references/rippled-api/public-rippled-methods/server-info-methods/server_state.md

@@ -37,7 +37,7 @@ rippled server_state
 
 <!-- MULTICODE_BLOCK_END -->
 
-[Try it! >](ripple-api-tool.html#server_state)
+[Try it! >](websocket-api-tool.html#server_state)
 
 The request does not takes any parameters.
 

content/references/rippled-api/public-rippled-methods/subscription-methods/subscribe.md

@@ -51,7 +51,7 @@ An example of the request format:
 
 <!-- MULTICODE_BLOCK_END -->
 
-[Try it! >](ripple-api-tool.html#subscribe)
+[Try it! >](websocket-api-tool.html#subscribe)
 
 The request includes the following parameters:
 

content/references/rippled-api/public-rippled-methods/subscription-methods/unsubscribe.md

@@ -34,7 +34,7 @@ An example of the request format:
 
 <!-- MULTICODE_BLOCK_END -->
 
-[Try it! >](ripple-api-tool.html#unsubscribe)
+[Try it! >](websocket-api-tool.html#unsubscribe)
 
 The parameters in the request are specified almost exactly like the parameters to [`subscribe`](#subscribe), except that they are used to define which subscriptions to end instead. The parameters are:
 

content/references/rippled-api/public-rippled-methods/transaction-methods/sign.md

@@ -66,7 +66,7 @@ rippled sign s██████████████████████
 
 <!-- MULTICODE_BLOCK_END -->
 
-[Try it! >](ripple-api-tool.html#sign)
+[Try it! >](websocket-api-tool.html#sign)
 
 To sign a transaction, you must provide a secret key that can [authorize the transaction](reference-transaction-format.html#authorizing-transactions). You can do this in a few ways:
 

content/references/rippled-api/public-rippled-methods/transaction-methods/submit.md

@@ -55,7 +55,7 @@ submit 1200002280000000240000000361D4838D7EA4C6800000000000000000000000000055534
 
 <!-- MULTICODE_BLOCK_END -->
 
-[Try it! >](ripple-api-tool.html#submit)
+[Try it! >](websocket-api-tool.html#submit)
 
 
 ## Sign-and-Submit Mode
@@ -146,7 +146,7 @@ rippled submit s█████████████████████
 
 <!-- MULTICODE_BLOCK_END -->
 
-[Try it! >](ripple-api-tool.html#submit)
+[Try it! >](websocket-api-tool.html#submit)
 
 ## Response Format
 

content/references/rippled-api/public-rippled-methods/transaction-methods/transaction_entry.md

@@ -43,7 +43,7 @@ rippled transaction_entry E08D6E9754025BA2534A78707605E0601F03ACE063687A0CA1BDDA
 
 <!-- MULTICODE_BLOCK_END -->
 
-[Try it! >](ripple-api-tool.html#transaction_entry)
+[Try it! >](websocket-api-tool.html#transaction_entry)
 
 The request includes the following parameters:
 

content/references/rippled-api/public-rippled-methods/transaction-methods/tx.md

@@ -41,7 +41,7 @@ rippled tx E08D6E9754025BA2534A78707605E0601F03ACE063687A0CA1BDDACFCD1698C7 fals
 
 <!-- MULTICODE_BLOCK_END -->
 
-[Try it! >](ripple-api-tool.html#tx)
+[Try it! >](websocket-api-tool.html#tx)
 
 The request includes the following parameters:
 

content/references/rippled-api/public-rippled-methods/transaction-methods/tx_history.md

@@ -42,7 +42,7 @@ rippled tx_history 0
 
 <!-- MULTICODE_BLOCK_END -->
 
-[Try it! >](ripple-api-tool.html#tx_history)
+[Try it! >](websocket-api-tool.html#tx_history)
 
 The request includes the following parameters:
 

content/references/rippled-api/public-rippled-methods/utility-methods/ping.md

@@ -37,7 +37,7 @@ rippled ping
 
 <!-- MULTICODE_BLOCK_END -->
 
-[Try it! >](ripple-api-tool.html#ping)
+[Try it! >](websocket-api-tool.html#ping)
 
 The request includes no parameters.