Rename rippled-api.html reference page

2025-11-27 07:05:51 +00:00 · 2022-06-28 03:45:56 -07:00
parent a91a2dd4e0
commit 42117756c6
82 changed files with 120 additions and 109 deletions
--- a/content/tutorials/get-started/get-started-using-http-websocket-apis.ja.md
+++ b/content/tutorials/get-started/get-started-using-http-websocket-apis.ja.md
@@ -233,5 +233,5 @@ HTTP Status:200 OK
  - [信頼できるトランザクションの送信](reliable-transaction-submission.html)
  - [rippledサーバーの管理](manage-the-rippled-server.html)
 - **リファレンス:**
-  - [rippled APIリファレンス](rippled-api.html)
+  - [rippled APIリファレンス](http-websocket-apis.html)
  - [Ripple Data API v2](data-api.html)
--- a/content/tutorials/get-started/get-started-using-http-websocket-apis.md
+++ b/content/tutorials/get-started/get-started-using-http-websocket-apis.md
@@ -107,7 +107,7 @@ For a full list of API methods, see:
    - [Reliable Transaction Submission](reliable-transaction-submission.html)
    - [Manage the rippled Server](manage-the-rippled-server.html)
 - **References:**
-    - [rippled API Reference](rippled-api.html)
+    - [rippled API Reference](http-websocket-apis.html)

 <!--{# common link defs #}-->
 {% include '_snippets/rippled-api-links.md' %}			
--- a/content/tutorials/get-started/monitor-incoming-payments-with-websocket.ja.md
+++ b/content/tutorials/get-started/monitor-incoming-payments-with-websocket.ja.md
@@ -9,7 +9,7 @@ labels:
 ---
 # WebSocketを使用した着信ペイメントの監視

-このチュートリアルでは、[WebSocket `rippled` API](rippled-api.html)を使用して、着信[ペイメント](payment-types.html)を監視する方法を説明します。すべてのXRP Ledgerトランザクションは公開されているため、誰もが任意のアドレスへの着信ペイメントを監視できます。
+このチュートリアルでは、[WebSocket `rippled` API](http-websocket-apis.html)を使用して、着信[ペイメント](payment-types.html)を監視する方法を説明します。すべてのXRP Ledgerトランザクションは公開されているため、誰もが任意のアドレスへの着信ペイメントを監視できます。

 WebSocketは、クライアントとサーバーが1つの接続を確立し、その接続を経由して両方向にメッセージを送信するモデルに従います。この接続は、明示的に閉じる（または接続に障害が発生する）まで続きます。これは、要求ごとにクライアントが新しい接続を開いて閉じるHTTPベースのAPIモデル（JSON-RPCやRESTful APIなど）とは対照的です[¹](#footnote-1)<a id="from-footnote-1"></a>。

--- a/content/tutorials/get-started/monitor-incoming-payments-with-websocket.md
+++ b/content/tutorials/get-started/monitor-incoming-payments-with-websocket.md
@@ -9,7 +9,7 @@ labels:
 ---
 # Monitor Incoming Payments with WebSocket

-This tutorial shows how to monitor for incoming [payments](payment-types.html) using the [WebSocket `rippled` API](rippled-api.html). Since all XRP Ledger transactions are public, anyone can monitor incoming payments to any address.
+This tutorial shows how to monitor for incoming [payments](payment-types.html) using the [WebSocket `rippled` API](http-websocket-apis.html). Since all XRP Ledger transactions are public, anyone can monitor incoming payments to any address.

 WebSocket follows a model where the client and server establish one connection, then send messages both ways through the same connection, which remains open until explicitly closed (or until the connection fails). This is in contrast to the HTTP-based API model (including JSON-RPC and RESTful APIs), where the client opens and closes a new connection for each request.[¹](#footnote-1)<a id="from-footnote-1"></a>

--- a/content/tutorials/manage-the-clio-server/build-run-clio-ubuntu.md
+++ b/content/tutorials/manage-the-clio-server/build-run-clio-ubuntu.md
@@ -195,7 +195,7 @@ Watchdog: Launching child 1

 * Now that you have a stock `rippled` server running, you may want to consider running it as a validating server. For information about validating servers and why you might want to run one, see the [rippled Setup Tutorial](install-rippled.html).

-* For information about communicating with your `rippled` server using the `rippled` API, see the [`rippled` API reference](rippled-api.html).
+* For information about communicating with your `rippled` server using the `rippled` API, see the [`rippled` API reference](http-websocket-apis.html).

 * As a development best practice, you may want to build a `rippled` `.deb` package. You can use the CMake build's deb package target to build a `deb` package directly from the source tree. The build machine must have [Docker installed](https://docs.docker.com/install/#supported-platforms). This process may take more than an hour to complete. To build the `deb` package:

@@ -215,7 +215,7 @@ Watchdog: Launching child 1
    - [Troubleshoot rippled](troubleshoot-the-rippled-server.html)
    - [Get Started with the rippled API](get-started-using-http-websocket-apis.html)
 - **References:**
-    - [rippled API Reference](rippled-api.html)
+    - [rippled API Reference](http-websocket-apis.html)
        - [`rippled` Commandline Usage](commandline-usage.html)
        - [server_info method][]

--- a/content/tutorials/manage-the-rippled-server/configuration/configure-grpc.md
+++ b/content/tutorials/manage-the-rippled-server/configuration/configure-grpc.md
@@ -7,7 +7,7 @@ labels:
 ---
 # Configure gRPC

-The `rippled` server has an experimental [gRPC API](https://grpc.io/). Currently, this API provides a subset of the full [`rippled` API](rippled-api.html). You can enable the gRPC API on your server with a new configuration stanza. [New in: rippled 1.5.0][]
+The `rippled` server has an experimental [gRPC API](https://grpc.io/). Currently, this API provides a subset of the full [`rippled` API](http-websocket-apis.html). You can enable the gRPC API on your server with a new configuration stanza. [New in: rippled 1.5.0][]

 **Caution:** gRPC support in `rippled` v1.5.0 is experimental. Configuration settings and API formats are likely to have breaking changes in forthcoming versions.

@@ -52,7 +52,7 @@ To enable gRPC on your server, complete the following steps:
    - [Reliable Transaction Submission](reliable-transaction-submission.html)
    - [Manage the rippled Server](manage-the-rippled-server.html)
 - **References:**
-    - [rippled API Reference](rippled-api.html)
+    - [rippled API Reference](http-websocket-apis.html)
    - [Ripple Data API v2](data-api.html)

 <!--{# common link defs #}-->
--- a/content/tutorials/manage-the-rippled-server/installation/build-run-rippled-in-reporting-mode.md
+++ b/content/tutorials/manage-the-rippled-server/installation/build-run-rippled-in-reporting-mode.md
@@ -9,7 +9,7 @@ top_nav_grouping: Popular Pages
 ---
 # Build and Run `rippled` in Reporting Mode

-[Reporting mode](rippled-server-modes.html) is a mode of the XRP Ledger core server specialized for serving [HTTP and WebSocket APIs](rippled-api.html).
+[Reporting mode](rippled-server-modes.html) is a mode of the XRP Ledger core server specialized for serving [HTTP and WebSocket APIs](http-websocket-apis.html).

 In reporting mode, the server does not connect to the peer-to-peer network. Instead, it uses gRPC to get validated data from one or more trusted servers that are connected to the P2P network. 

--- a/content/tutorials/manage-the-rippled-server/installation/build-run-rippled-macos.ja.md
+++ b/content/tutorials/manage-the-rippled-server/installation/build-run-rippled-macos.ja.md
@@ -185,7 +185,7 @@ labels:
    - [rippledのトラブルシューティング](troubleshoot-the-rippled-server.html)
    - [rippled APIの使用開始](get-started-using-http-websocket-apis.html)
 - **リファレンス:**
-    - [rippled APIリファレンス](rippled-api.html)
+    - [rippled APIリファレンス](http-websocket-apis.html)
      - [`rippled`コマンドラインの使用](commandline-usage.html)
      - [server_infoメソッド][]

--- a/content/tutorials/manage-the-rippled-server/installation/build-run-rippled-macos.md
+++ b/content/tutorials/manage-the-rippled-server/installation/build-run-rippled-macos.md
@@ -199,7 +199,7 @@ For information about `rippled` log messages, see [Understanding Log Messages](u
    - [Troubleshoot rippled](troubleshoot-the-rippled-server.html)
    - [Get Started with the rippled API](get-started-using-http-websocket-apis.html)
 - **References:**
-    - [rippled API Reference](rippled-api.html)
+    - [rippled API Reference](http-websocket-apis.html)
        - [`rippled` Commandline Usage](commandline-usage.html)
        - [server_info method][]

--- a/content/tutorials/manage-the-rippled-server/installation/build-run-rippled-ubuntu.ja.md
+++ b/content/tutorials/manage-the-rippled-server/installation/build-run-rippled-ubuntu.ja.md
@@ -204,7 +204,7 @@ Watchdog: Launching child 1

 * これでストック`rippled`サーバーを実行できたので、次に検証サーバーとして実行してみましょう。検証サーバーの詳細について、そして検証サーバーを実行する理由については、[rippledのセットアップチュートリアル](install-rippled.html)を参照してください。

-* `rippled` APIを使用して`rippled`サーバーと通信する方法については、[`rippled` APIリファレンス](rippled-api.html)を参照してください。
+* `rippled` APIを使用して`rippled`サーバーと通信する方法については、[`rippled` APIリファレンス](http-websocket-apis.html)を参照してください。

 * 開発のベストプラクティスとして、`rippled` `.deb`パッケージをビルドすることをお勧めします。CMakeビルドのdebパッケージターゲットを使用して、ソースツリーから直接`deb`パッケージをビルドできます。ビルドマシンには[Dockerをインストール](https://docs.docker.com/install/#supported-platforms)している必要があります。このプロセスを完了するのに1時間以上かかる場合があります。`deb`パッケージをビルドするには、以下の手順に従います。

@@ -224,7 +224,7 @@ Watchdog: Launching child 1
    - [rippledのトラブルシューティング](troubleshoot-the-rippled-server.html)
    - [rippled APIの使用開始](get-started-using-http-websocket-apis.html)
 - **リファレンス:**
-    - [rippled APIリファレンス](rippled-api.html)
+    - [rippled APIリファレンス](http-websocket-apis.html)
      - [`rippled`コマンドラインの使用](commandline-usage.html)
      - [server_infoメソッド][]

--- a/content/tutorials/manage-the-rippled-server/installation/build-run-rippled-ubuntu.md
+++ b/content/tutorials/manage-the-rippled-server/installation/build-run-rippled-ubuntu.md
@@ -199,7 +199,7 @@ Watchdog: Launching child 1

 * Now that you have a stock `rippled` server running, you may want to consider running it as a validating server. For information about validating servers and why you might want to run one, see the [rippled Setup Tutorial](install-rippled.html).

-* For information about communicating with your `rippled` server using the `rippled` API, see the [`rippled` API reference](rippled-api.html).
+* For information about communicating with your `rippled` server using the `rippled` API, see the [`rippled` API reference](http-websocket-apis.html).

 * As a development best practice, you may want to build a `rippled` `.deb` package. You can use the CMake build's deb package target to build a `deb` package directly from the source tree. The build machine must have [Docker installed](https://docs.docker.com/install/#supported-platforms). This process may take more than an hour to complete. To build the `deb` package:

@@ -219,7 +219,7 @@ Watchdog: Launching child 1
    - [Troubleshoot rippled](troubleshoot-the-rippled-server.html)
    - [Get Started with the rippled API](get-started-using-http-websocket-apis.html)
 - **References:**
-    - [rippled API Reference](rippled-api.html)
+    - [rippled API Reference](http-websocket-apis.html)
        - [`rippled` Commandline Usage](commandline-usage.html)
        - [server_info method][]

--- a/content/tutorials/manage-the-rippled-server/installation/capacity-planning.ja.md
+++ b/content/tutorials/manage-the-rippled-server/installation/capacity-planning.ja.md
@@ -10,7 +10,7 @@ labels:

 このドキュメントでは、XRP Ledgerサーバーのパフォーマンスを調整・最適化するために使用できる、構成、ネットワーク、ハードウェアに関する推奨事項を説明しています。

-XRP Ledgerのサーバーの負荷は、複数の要因によって変化します。ひとつは、ネットワーク内の活動です。共有レジャーのデータサイズや送信されるトランザクションの総量は、グローバルなXRP Ledgerコミュニティ全体の有機的な要因に基づいて変化します。もうひとつの要因は、APIの使用状況です。異なる種類の[APIコール](rippled-api.html)は、サーバーに異なる負荷をかけます。パブリックなAPIを提供しているサーバーと、特定の統合ソフトウェアにプライベートなAPIを提供しているサーバー、あるいはAPIを全く提供していないサーバーとでは、パフォーマンス特性が大きく異なります。
+XRP Ledgerのサーバーの負荷は、複数の要因によって変化します。ひとつは、ネットワーク内の活動です。共有レジャーのデータサイズや送信されるトランザクションの総量は、グローバルなXRP Ledgerコミュニティ全体の有機的な要因に基づいて変化します。もうひとつの要因は、APIの使用状況です。異なる種類の[APIコール](http-websocket-apis.html)は、サーバーに異なる負荷をかけます。パブリックなAPIを提供しているサーバーと、特定の統合ソフトウェアにプライベートなAPIを提供しているサーバー、あるいはAPIを全く提供していないサーバーとでは、パフォーマンス特性が大きく異なります。

 これらの要素を考慮して、構成するサーバーが現在および将来のXRP Ledgerネットワークの活動を処理する能力を持っていることを確認する必要があります。

@@ -206,7 +206,7 @@ AWSインスタンスストア（`ephemeral`ストレージ）では適切なパ
        - [オンライ削除の設定](configure-online-deletion.html) - サーバーが一度に保持するレジャー履歴のバージョン数を調整します。
    - [`rippled`のトラブルシューティング](troubleshoot-the-rippled-server.html)
 - **リファレンス:**
-    - [rippled APIリファレンス](rippled-api.html)
+    - [rippled APIリファレンス](http-websocket-apis.html)
      - [`rippled`コマンドラインの使用](commandline-usage.html)
        - [logrotate メソッド][] - サーバーのデバッグログを閉じたり再開したりして、標準的なツールでローテーション可能にします。
        - [server_info メソッド][] - 同期の状態や、ディスク上で利用可能なレジャー履歴のバージョン数など、サーバーに関する一般的な情報を取得します。
--- a/content/tutorials/manage-the-rippled-server/installation/capacity-planning.md
+++ b/content/tutorials/manage-the-rippled-server/installation/capacity-planning.md
@@ -10,7 +10,7 @@ labels:

 This document describes configuration, network, and hardware recommendations that you can use to tune and optimize the performance of an XRP Ledger server.

-The load on an XRP Ledger server varies based on multiple factors. One is the activity in the network. The total size of data in the shared ledger and the total volume of transactions being sent vary based on organic factors throughout the global XRP Ledger community. Another factor is API usage; different types of [API calls](rippled-api.html) put different load on the server. The performance characteristics can be very different between servers that provide a public API, provide a private API to specific integration software, or provide no API at all.
+The load on an XRP Ledger server varies based on multiple factors. One is the activity in the network. The total size of data in the shared ledger and the total volume of transactions being sent vary based on organic factors throughout the global XRP Ledger community. Another factor is API usage; different types of [API calls](http-websocket-apis.html) put different load on the server. The performance characteristics can be very different between servers that provide a public API, provide a private API to specific integration software, or provide no API at all.

 You should consider these factors to ensure that your server has the capacity to handle XRP Ledger network activity today and in the future.

@@ -204,7 +204,7 @@ You can save bandwidth by [enabling compression on peer-to-peer communications](
        - [Configure Online Deletion](configure-online-deletion.html) - Adjust how many historical ledger versions your server should keep at a time.
    - [Troubleshoot rippled](troubleshoot-the-rippled-server.html)
 - **References:**
-    - [rippled API Reference](rippled-api.html)
+    - [rippled API Reference](http-websocket-apis.html)
        - [`rippled` Commandline Usage](commandline-usage.html)
        - [logrotate method][] - Closes and reopens the server's debug log so you can rotate it with standard tools.
        - [server_info method][] - General information about the server including sync status and how many historical ledger versions it has available on disk.
--- a/content/tutorials/manage-the-rippled-server/installation/install-rippled-on-centos-rhel-with-yum.ja.md
+++ b/content/tutorials/manage-the-rippled-server/installation/install-rippled-on-centos-rhel-with-yum.ja.md
@@ -69,7 +69,7 @@ labels:
    - [rippledのトラブルシューティング](troubleshoot-the-rippled-server.html)
    - [rippled APIの使用開始](get-started-using-http-websocket-apis.html)
 - **リファレンス:**
-    - [rippled APIリファレンス](rippled-api.html)
+    - [rippled APIリファレンス](http-websocket-apis.html)
      - [`rippled`コマンドラインの使用](commandline-usage.html)
      - [server_infoメソッド][]

--- a/content/tutorials/manage-the-rippled-server/installation/install-rippled-on-centos-rhel-with-yum.md
+++ b/content/tutorials/manage-the-rippled-server/installation/install-rippled-on-centos-rhel-with-yum.md
@@ -117,7 +117,7 @@ Before you install `rippled`, you must meet the [System Requirements](system-req
    - [Troubleshoot rippled](troubleshoot-the-rippled-server.html)
    - [Get Started with the rippled API](get-started-using-http-websocket-apis.html)
 - **References:**
-    - [rippled API Reference](rippled-api.html)
+    - [rippled API Reference](http-websocket-apis.html)
        - [`rippled` Commandline Usage](commandline-usage.html)
        - [server_info method][]

--- a/content/tutorials/manage-the-rippled-server/installation/install-rippled-on-ubuntu.ja.md
+++ b/content/tutorials/manage-the-rippled-server/installation/install-rippled-on-ubuntu.ja.md
@@ -103,7 +103,7 @@ labels:
    - [rippledのトラブルシューティング](troubleshoot-the-rippled-server.html)
    - [rippled APIの使用開始](get-started-using-http-websocket-apis.html)
 - **リファレンス:**
-    - [rippled APIリファレンス](rippled-api.html)
+    - [rippled APIリファレンス](http-websocket-apis.html)
      - [`rippled`コマンドラインの使用](commandline-usage.html)
      - [server_infoメソッド][]

--- a/content/tutorials/manage-the-rippled-server/installation/install-rippled-on-ubuntu.md
+++ b/content/tutorials/manage-the-rippled-server/installation/install-rippled-on-ubuntu.md
@@ -111,7 +111,7 @@ Before you install `rippled`, you must meet the [System Requirements](system-req
    - [Troubleshoot rippled](troubleshoot-the-rippled-server.html)
    - [Get Started with the rippled API](get-started-using-http-websocket-apis.html)
 - **References:**
-    - [rippled API Reference](rippled-api.html)
+    - [rippled API Reference](http-websocket-apis.html)
        - [`rippled` Commandline Usage](commandline-usage.html)
        - [server_info method][]

--- a/content/tutorials/manage-the-rippled-server/installation/rippled-1-3-migration-instructions.ja.md
+++ b/content/tutorials/manage-the-rippled-server/installation/rippled-1-3-migration-instructions.ja.md
@@ -100,7 +100,7 @@ Rippleの公式RPMリポジトリとそれを使用するための手順が変
  - [rippledのトラブルシューティング](troubleshoot-the-rippled-server.html)
  - [rippled APIの使用開始](get-started-using-http-websocket-apis.html)
 - **リファレンス:**
-    - [rippled APIリファレンス](rippled-api.html)
+    - [rippled APIリファレンス](http-websocket-apis.html)
      - [`rippled`コマンドラインの使用](commandline-usage.html)
      - [server_infoメソッド][]

--- a/content/tutorials/manage-the-rippled-server/installation/rippled-1-3-migration-instructions.md
+++ b/content/tutorials/manage-the-rippled-server/installation/rippled-1-3-migration-instructions.md
@@ -101,7 +101,7 @@ The `rippled` v1.3 package includes an updated auto-update script that works on
    - [Troubleshoot rippled](troubleshoot-the-rippled-server.html)
    - [Get Started with the rippled API](get-started-using-http-websocket-apis.html)
 - **References:**
-    - [rippled API Reference](rippled-api.html)
+    - [rippled API Reference](http-websocket-apis.html)
        - [`rippled` Commandline Usage](commandline-usage.html)
        - [server_info method][]

--- a/content/tutorials/manage-the-rippled-server/installation/system-requirements.ja.md
+++ b/content/tutorials/manage-the-rippled-server/installation/system-requirements.ja.md
@@ -45,7 +45,7 @@ labels:
    - [`rippled`のインストール](install-rippled.html)
    - [rippledのトラブルシューティング](troubleshoot-the-rippled-server.html)
 - **リファレンス:**
-    - [rippled APIリファレンス](rippled-api.html)
+    - [rippled APIリファレンス](http-websocket-apis.html)
      - [`rippled`コマンドラインの使用](commandline-usage.html)
      - [server_infoメソッド][]

--- a/content/tutorials/manage-the-rippled-server/installation/system-requirements.md
+++ b/content/tutorials/manage-the-rippled-server/installation/system-requirements.md
@@ -49,7 +49,7 @@ A `rippled` server relies on maintaining accurate time. It is recommended that t
    - [Install `rippled`](install-rippled.html)
    - [Troubleshoot rippled](troubleshoot-the-rippled-server.html)
 - **References:**
-    - [rippled API Reference](rippled-api.html)
+    - [rippled API Reference](http-websocket-apis.html)
        - [`rippled` Commandline Usage](commandline-usage.html)
        - [server_info method][]

--- a/content/tutorials/manage-the-rippled-server/installation/update-rippled-automatically-on-linux.ja.md
+++ b/content/tutorials/manage-the-rippled-server/installation/update-rippled-automatically-on-linux.ja.md
@@ -40,7 +40,7 @@ Linuxでは、`rippled`が1回限りの`cron`構成を使用して最新バー
    - [容量の計画](capacity-planning.html)
    - [rippledのトラブルシューティング](troubleshoot-the-rippled-server.html)
 - **リファレンス:**
-    - [rippled APIリファレンス](rippled-api.html)
+    - [rippled APIリファレンス](http-websocket-apis.html)
      - [`rippled`コマンドラインの使用](commandline-usage.html)
      - [server_infoメソッド][]

--- a/content/tutorials/manage-the-rippled-server/installation/update-rippled-automatically-on-linux.md
+++ b/content/tutorials/manage-the-rippled-server/installation/update-rippled-automatically-on-linux.md
@@ -38,7 +38,7 @@ To set up automatic updates, complete the following steps:
    - [Capacity Planning](capacity-planning.html)
    - [Troubleshoot rippled](troubleshoot-the-rippled-server.html)
 - **References:**
-    - [rippled API Reference](rippled-api.html)
+    - [rippled API Reference](http-websocket-apis.html)
        - [`rippled` Commandline Usage](commandline-usage.html)
        - [server_info method][]

--- a/content/tutorials/manage-the-rippled-server/installation/update-rippled-manually-on-centos-rhel.ja.md
+++ b/content/tutorials/manage-the-rippled-server/installation/update-rippled-manually-on-centos-rhel.ja.md
@@ -50,7 +50,7 @@ labels:
    - [`rippled` v1.3.xへの移行手順](rippled-1-3-migration-instructions.html) <!-- Note: remove when versions older than v1.3 are basically extinct -->
    - [rippledのトラブルシューティング](troubleshoot-the-rippled-server.html)
 - **リファレンス:**
-    - [rippled APIリファレンス](rippled-api.html)
+    - [rippled APIリファレンス](http-websocket-apis.html)
      - [`rippled`コマンドラインの使用](commandline-usage.html)
      - [server_infoメソッド][]

--- a/content/tutorials/manage-the-rippled-server/installation/update-rippled-manually-on-centos-rhel.md
+++ b/content/tutorials/manage-the-rippled-server/installation/update-rippled-manually-on-centos-rhel.md
@@ -52,7 +52,7 @@ To update manually, complete the following steps:
    - [`rippled` v1.3.x Migration Instructions](rippled-1-3-migration-instructions.html) <!-- Note: remove when versions older than v1.3 are basically extinct -->
    - [Troubleshoot rippled](troubleshoot-the-rippled-server.html)
 - **References:**
-    - [rippled API Reference](rippled-api.html)
+    - [rippled API Reference](http-websocket-apis.html)
        - [`rippled` Commandline Usage](commandline-usage.html)
        - [server_info method][]

--- a/content/tutorials/manage-the-rippled-server/installation/update-rippled-manually-on-ubuntu.ja.md
+++ b/content/tutorials/manage-the-rippled-server/installation/update-rippled-manually-on-ubuntu.ja.md
@@ -42,7 +42,7 @@ labels:
    - [`rippled` v1.3.xへの移行手順](rippled-1-3-migration-instructions.html) <!-- Note: remove when versions older than v1.3 are basically extinct -->
    - [rippledのトラブルシューティング](troubleshoot-the-rippled-server.html)
 - **リファレンス:**
-    - [rippled APIリファレンス](rippled-api.html)
+    - [rippled APIリファレンス](http-websocket-apis.html)
      - [`rippled`コマンドラインの使用](commandline-usage.html)
      - [server_infoメソッド][]

--- a/content/tutorials/manage-the-rippled-server/installation/update-rippled-manually-on-ubuntu.md
+++ b/content/tutorials/manage-the-rippled-server/installation/update-rippled-manually-on-ubuntu.md
@@ -47,7 +47,7 @@ To update manually, complete the following steps:
    - [`rippled` v1.3.x Migration Instructions](rippled-1-3-migration-instructions.html) <!-- Note: remove when versions older than v1.3 are basically extinct -->
    - [Troubleshoot rippled](troubleshoot-the-rippled-server.html)
 - **References:**
-    - [rippled API Reference](rippled-api.html)
+    - [rippled API Reference](http-websocket-apis.html)
        - [`rippled` Commandline Usage](commandline-usage.html)
        - [server_info method][]

--- a/content/tutorials/manage-the-rippled-server/troubleshooting/diagnosing-problems.ja.md
+++ b/content/tutorials/manage-the-rippled-server/troubleshooting/diagnosing-problems.ja.md
@@ -125,7 +125,7 @@ rippled server_info
    - [容量の計画](capacity-planning.html)
    - [rippledの構成](configure-rippled.html)
 - **リファレンス:**
-    - [rippled APIリファレンス](rippled-api.html)
+    - [rippled APIリファレンス](http-websocket-apis.html)
      - [`rippled`コマンドラインの使用](commandline-usage.html)
      - [log_levelメソッド][]
      - [server_infoメソッド][]
--- a/content/tutorials/manage-the-rippled-server/troubleshooting/diagnosing-problems.md
+++ b/content/tutorials/manage-the-rippled-server/troubleshooting/diagnosing-problems.md
@@ -168,7 +168,7 @@ To use the script:
    - [Capacity Planning](capacity-planning.html)
    - [Configure rippled](configure-rippled.html)
 - **References:**
-    - [rippled API Reference](rippled-api.html)
+    - [rippled API Reference](http-websocket-apis.html)
        - [`rippled` Commandline Usage](commandline-usage.html)
        - [log_level method][]
        - [server_info method][]
--- a/content/tutorials/manage-the-rippled-server/troubleshooting/fix-sqlite-tx-db-page-size-issue.md
+++ b/content/tutorials/manage-the-rippled-server/troubleshooting/fix-sqlite-tx-db-page-size-issue.md
@@ -182,7 +182,7 @@ To migrate your transaction database to a larger page size, perform the followin
    - [Understanding Log Messages](understanding-log-messages.html)
    - [Configure Full History](configure-full-history.html)
 - **References:**
-    - [rippled API Reference](rippled-api.html)
+    - [rippled API Reference](http-websocket-apis.html)
        - [`rippled` Commandline Usage](commandline-usage.html)
        - [server_info method][]

--- a/content/tutorials/manage-the-rippled-server/troubleshooting/server-doesnt-sync.ja.md
+++ b/content/tutorials/manage-the-rippled-server/troubleshooting/server-doesnt-sync.ja.md
@@ -104,7 +104,7 @@ labels:
    - [ログメッセージについて](understanding-log-messages.html)
    - [容量の計画](capacity-planning.html)
 - **リファレンス:**
-    - [rippled APIリファレンス](rippled-api.html)
+    - [rippled APIリファレンス](http-websocket-apis.html)
      - [peersメソッド][]
      - [server_infoメソッド][]
      - [validator_list_sitesメソッド][]
--- a/content/tutorials/manage-the-rippled-server/troubleshooting/server-doesnt-sync.md
+++ b/content/tutorials/manage-the-rippled-server/troubleshooting/server-doesnt-sync.md
@@ -108,7 +108,7 @@ As a test, you can temporarily change the paths to your server's databases as lo
    - [Understanding Log Messages](understanding-log-messages.html)
    - [Capacity Planning](capacity-planning.html)
 - **References:**
-    - [rippled API Reference](rippled-api.html)
+    - [rippled API Reference](http-websocket-apis.html)
        - [peers method][]
        - [server_info method][]
        - [validator_list_sites method][]
--- a/content/tutorials/manage-the-rippled-server/troubleshooting/server-wont-start.ja.md
+++ b/content/tutorials/manage-the-rippled-server/troubleshooting/server-wont-start.ja.md
@@ -211,7 +211,7 @@ ShardStore:ERR Unsupported shard store type: RocksDB
    - [ログメッセージについて](understanding-log-messages.html)
    - [容量の計画](capacity-planning.html)
 - **リファレンス:**
-    - [rippled APIリファレンス](rippled-api.html)
+    - [rippled APIリファレンス](http-websocket-apis.html)
      - [`rippled`コマンドラインの使用](commandline-usage.html)
      - [server_infoメソッド][]

--- a/content/tutorials/manage-the-rippled-server/troubleshooting/server-wont-start.md
+++ b/content/tutorials/manage-the-rippled-server/troubleshooting/server-wont-start.md
@@ -212,7 +212,7 @@ To fix this problem, do one of the following, then restart the server:
    - [Understanding Log Messages](understanding-log-messages.html)
    - [Capacity Planning](capacity-planning.html)
 - **References:**
-    - [rippled API Reference](rippled-api.html)
+    - [rippled API Reference](http-websocket-apis.html)
        - [`rippled` Commandline Usage](commandline-usage.html)
        - [server_info method][]

--- a/content/tutorials/manage-the-rippled-server/troubleshooting/understanding-log-messages.ja.md
+++ b/content/tutorials/manage-the-rippled-server/troubleshooting/understanding-log-messages.ja.md
@@ -224,7 +224,7 @@ NetworkOPs:WRN We are not running on the consensus ledger
    - [問題の診断](diagnosing-problems.html)
    - [容量の計画](capacity-planning.html)
 - **リファレンス:**
-    - [rippled APIリファレンス](rippled-api.html)
+    - [rippled APIリファレンス](http-websocket-apis.html)
      - [`rippled`コマンドラインの使用](commandline-usage.html)
      - [server_infoメソッド][]

--- a/content/tutorials/manage-the-rippled-server/troubleshooting/understanding-log-messages.md
+++ b/content/tutorials/manage-the-rippled-server/troubleshooting/understanding-log-messages.md
@@ -344,7 +344,7 @@ NetworkOPs:WRN We are not running on the consensus ledger
    - [Diagnosing Problems](diagnosing-problems.html)
    - [Capacity Planning](capacity-planning.html)
 - **References:**
-    - [rippled API Reference](rippled-api.html)
+    - [rippled API Reference](http-websocket-apis.html)
        - [`rippled` Commandline Usage](commandline-usage.html)
        - [server_info method][]

--- a/content/tutorials/production-readiness/reliable-transaction-submission.ja.md
+++ b/content/tutorials/production-readiness/reliable-transaction-submission.ja.md
@@ -33,7 +33,7 @@ XRP Ledgerプロトコルは、ネットワークのすべてのサーバーで

 ### トランザクションのタイムライン

-XRP Ledgerには、[HTTP / WebSocket API](rippled-api.html)や[クライアントライブラリ](client-libraries.html)など、トランザクションを送信するためのAPIがいくつかあります。使用するAPIにかかわらず、トランザクションは以下のようにレジャーに適用されます。
+XRP Ledgerには、[HTTP / WebSocket API](http-websocket-apis.html)や[クライアントライブラリ](client-libraries.html)など、トランザクションを送信するためのAPIがいくつかあります。使用するAPIにかかわらず、トランザクションは以下のようにレジャーに適用されます。

 1. アカウント所有者は、トランザクションを作成して署名します。
 2. 所有者は、トランザクション候補として、そのトランザクションをネットワークに送信します。
@@ -183,7 +183,7 @@ For each persisted transaction without validated result:

 アプリケーションでのこれらのアクションの実行方法は、アプリケーションが使用するAPIによって異なります。アプリケーションでは、以下のインターフェイスを使用できます。

-1. [HTTP / WebSocket API](rippled-api.html)
+1. [HTTP / WebSocket API](http-websocket-apis.html)
 2. [クライアントライブラリ](client-libraries.html)
 3. 任意の数の他のソフトウェアAPI

--- a/content/tutorials/production-readiness/reliable-transaction-submission.md
+++ b/content/tutorials/production-readiness/reliable-transaction-submission.md
@@ -36,7 +36,7 @@ If a power or network outage occurs, applications face more challenges finding t

 ### Transaction Timeline

-When you submit a transaction to the XRP Ledger, regardless of whether you used [HTTP API](rippled-api.html), a [client library](client-libraries.html), or some other app, process of applying the transaction to the ledger is the same. That process goes like this:
+When you submit a transaction to the XRP Ledger, regardless of whether you used [HTTP API](http-websocket-apis.html), a [client library](client-libraries.html), or some other app, process of applying the transaction to the ledger is the same. That process goes like this:

 1. An account owner creates and signs a transaction.
 2. The owner submits the transaction to the network as a candidate transaction.
@@ -68,7 +68,7 @@ Each validated ledger has a canonical order in which transactions apply. This or

 Use the `LastLedgerSequence` parameter to prevent undesirable cases where a transaction is not confirmed promptly but could be included in a future ledger.  You should specify the `LastLedgerSequence` parameter on every transaction.  Automated processes should use a value of 4 greater than the last validated ledger index to make sure that a transaction is validated or rejected in a predictable and prompt way.

-Applications using the [HTTP / WebSocket APIs](rippled-api.html) should explicitly specify a `LastLedgerSequence` when submitting transactions. Some [client libraries](client-libraries.html) can also [auto-fill](transaction-common-fields.html#auto-fillable-fields) a reasonable value for `LastLedgerSequence`; the details vary by library.
+Applications using the [HTTP / WebSocket APIs](http-websocket-apis.html) should explicitly specify a `LastLedgerSequence` when submitting transactions. Some [client libraries](client-libraries.html) can also [auto-fill](transaction-common-fields.html#auto-fillable-fields) a reasonable value for `LastLedgerSequence`; the details vary by library.



@@ -198,7 +198,7 @@ To implement the transaction submission and verification best practices, applica

 How the application does these actions depends on the API the application uses.  An application may use any of the following interfaces:

- The [HTTP / WebSocket APIs](rippled-api.html) provided directly by XRP Ledger servers
+- The [HTTP / WebSocket APIs](http-websocket-apis.html) provided directly by XRP Ledger servers
 - A [client library](client-libraries.html)
 - Other middleware or APIs layered on top of the above APIs

--- a/content/tutorials/use-specialized-payment-types/use-payment-channels.ja.md
+++ b/content/tutorials/use-specialized-payment-types/use-payment-channels.ja.md
@@ -8,7 +8,7 @@ labels:
 ---
 # Payment Channelの使用

-Payment Channelは、少額の単位に分割可能な「非同期」のXRPペイメントを送信し、後日決済する高度な機能です。このチュートリアルでは、全体的な[Payment Channel](payment-channels.html)の使用方法を、ローカル`rippled`サーバーの[JSON-RPC API](rippled-api.html)を使用する例を使って説明します。
+Payment Channelは、少額の単位に分割可能な「非同期」のXRPペイメントを送信し、後日決済する高度な機能です。このチュートリアルでは、全体的な[Payment Channel](payment-channels.html)の使用方法を、ローカル`rippled`サーバーの[JSON-RPC API](http-websocket-apis.html)を使用する例を使って説明します。

 このチュートリアルを進めるにあたって[資金供給されているXRP Ledgerアカウント](accounts.html)を所有するユーザーが2名いれば理想的です。ただし、2つのXRP Ledgerアドレスを管理する1名のユーザーとしてこのチュートリアルを進めることもできます。

--- a/content/tutorials/use-specialized-payment-types/use-payment-channels.md
+++ b/content/tutorials/use-specialized-payment-types/use-payment-channels.md
@@ -8,7 +8,7 @@ labels:
 ---
 # Use Payment Channels

-[Payment Channels](payment-channels.html) are an advanced feature for sending "asynchronous" XRP payments that can be divided into very small increments and settled later. This tutorial walks through the entire process of using a payment channel, with examples using the [JSON-RPC API](rippled-api.html) of a local [`rippled` server](xrpl-servers.html).
+[Payment Channels](payment-channels.html) are an advanced feature for sending "asynchronous" XRP payments that can be divided into very small increments and settled later. This tutorial walks through the entire process of using a payment channel, with examples using the [JSON-RPC API](http-websocket-apis.html) of a local [`rippled` server](xrpl-servers.html).

 Ideally, to step through this tutorial, you would have two people, each with the keys to a [funded XRP Ledger account](accounts.html). However, you can also step through the tutorial as one person managing two XRP Ledger addresses.

--- a/content/tutorials/xrp-ledger-businesses/become-an-xrp-ledger-gateway.md
+++ b/content/tutorials/xrp-ledger-businesses/become-an-xrp-ledger-gateway.md
@@ -46,7 +46,7 @@ The XRP Ledger contains a [decentralized asset exchange](decentralized-exchange.

 Currency traders who hold a gateway's issued currencies can provide liquidity to other popular currencies, without the gateway needing to float a large reserve in various destination currencies. The gateway also does not need to take on the risk of holding a variety of currencies. However, a gateway _may_ still want to provide liquidity to XRP or other popular currencies at a baseline rate, especially when the gateway is new to the exchange. If you do provide liquidity, **use a different address for trading than your issuing address.**

-Liquidity providers can use the [HTTP / WebSocket APIs](rippled-api.html), [client libraries](client-libraries.html), or another application to access the distributed exchange. It may also help client applications to surface information about your gateway to clients if you provide an [`xrp-ledger.toml` file](xrp-ledger-toml.html).
+Liquidity providers can use the [HTTP / WebSocket APIs](http-websocket-apis.html), [client libraries](client-libraries.html), or another application to access the distributed exchange. It may also help client applications to surface information about your gateway to clients if you provide an [`xrp-ledger.toml` file](xrp-ledger-toml.html).



@@ -379,7 +379,7 @@ For the gateway's own security as well as the stability of the network, each gat

 There are several interfaces you can use to connect to the XRP Ledger, depending on your needs and your existing software:

-* [`rippled`](rippled-api.html) provides JSON-RPC and WebSocket APIs that can be used as a low-level interface to all core XRP Ledger functionality.
+* [`rippled`](http-websocket-apis.html) provides JSON-RPC and WebSocket APIs that can be used as a low-level interface to all core XRP Ledger functionality.
 * [Client Libraries](client-libraries.html) are available in several programming languages to provide convenient utilities for accessing the XRP Ledger.
 * Other tools such as [xApps](https://xumm.readme.io/docs/xapps) are also available.