Skip to content

Commit c528649

Browse files
authored
Merge pull request #2956 from XRPLF/api-versions-update
Update API Versions doc
2 parents 2d047d1 + 075cfdf commit c528649

File tree

1 file changed

+3
-1
lines changed
  • docs/references/http-websocket-apis

1 file changed

+3
-1
lines changed

docs/references/http-websocket-apis/index.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,8 @@ Currently, there are two API versions: `1` and `2` {% badge href="https://github
1212

1313
Separate API requests can use different API versions even on the same persistent connection. For example, if you connect through WebSocket to a server that supports API versions 1 and 2, you can make an `account_tx` request using API version 2 and then make another `account_tx` request using API version 1 from the same connection.
1414

15+
For a full list of the differences between API versions, see [API-CHANGELOG on GitHub](https://github.com/xrplf/rippled/blob/develop/API-CHANGELOG.md).
16+
1517

1618
## Default API Versions
1719

@@ -26,7 +28,7 @@ The table below shows which version of the `rippled` API is used if you don't sp
2628
| [xrpl-py](https://github.com/XRPLF/xrpl-py) | 2 | Defaults to [API v2][] starting in v3.0.0. |
2729

2830
{% admonition type="info" name="Note" %}
29-
Clio responses use [API v1][] by default, but support [API v2][] requests.
31+
Clio behaves the same as `rippled`.
3032
{% /admonition %}
3133

3234
Future versions of `rippled` that introduce breaking changes will introduce a new API version 3.

0 commit comments

Comments
 (0)