From 8005d30f0e4b71d0b387b45f0b55b9b0d90ffe82 Mon Sep 17 00:00:00 2001 From: Mayukha Vadari Date: Tue, 18 Feb 2025 22:00:28 -0500 Subject: [PATCH] Update account_tx.md --- .../public-api-methods/account-methods/account_tx.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/docs/references/http-websocket-apis/public-api-methods/account-methods/account_tx.md b/docs/references/http-websocket-apis/public-api-methods/account-methods/account_tx.md index ed94f5627a..8a23221220 100644 --- a/docs/references/http-websocket-apis/public-api-methods/account-methods/account_tx.md +++ b/docs/references/http-websocket-apis/public-api-methods/account-methods/account_tx.md @@ -440,7 +440,6 @@ The response follows the [standard format][], with a successful result containin | `limit` | Integer | The `limit` value used in the request. (This may differ from the actual limit value enforced by the server.) | | `marker` | [Marker][] | Server-defined value indicating the response is paginated. Pass this to the next call to resume where this call left off. | | `transactions` | Array | Array of transactions matching the request's criteria, as explained below. | -| `validated` | Boolean | If included and set to `true`, the information in this response comes from a validated ledger version. Otherwise, the information is subject to change. | {% admonition type="info" name="Note" %}The server may respond with different values of `ledger_index_min` and `ledger_index_max` than you provided in the request, for example if it did not have the versions you specified on hand.{% /admonition %} @@ -469,9 +468,7 @@ Each transaction object includes the following fields, depending on whether it w | `ledger_index_max` | Integer - [Ledger Index][] | The ledger index of the most recent ledger actually searched for transactions. | | `limit` | Integer | The `limit` value used in the request. (This may differ from the actual limit value enforced by the server.) | | `marker` | [Marker][] | Server-defined value indicating the response is paginated. Pass this to the next call to resume where this call left off. | -| `meta` | Object (JSON) or String (Binary) | If `binary` is `true`, then this is a hex string of the transaction results metadata. Otherwise, the transaction results metadata is included in JSON format. | | `transactions` | Array | Array of transactions matching the request's criteria, as explained below. | -| `validated` | Boolean | If included and set to `true`, the information in this response comes from a validated ledger version. Otherwise, the information is subject to change. | {% admonition type="info" name="Note" %}The server may respond with different values of `ledger_index_min` and `ledger_index_max` than you provided in the request, for example if it did not have the versions you specified on hand.{% /admonition %} @@ -482,6 +479,7 @@ Each transaction object includes the following fields, depending on whether it w | `ledger_index` | Integer | The [ledger index][] of the ledger version that included this transaction. | | `tx` | Object | (JSON mode) JSON object defining the transaction. | | `tx_blob` | String | (Binary mode) Hex string representing the transaction. | +| `meta` | Object (JSON) or String (Binary) | If `binary` is `true`, then this is a hex string of the transaction results metadata. Otherwise, the transaction results metadata is included in JSON format. | | `validated` | Boolean | Whether or not the transaction is included in a validated ledger. Any transaction not yet in a validated ledger is subject to change. | {% /tab %}