ARCHIVE/xrpl-dev-portal
1
0
Fork 0
mirror of https://github.com/XRPLF/xrpl-dev-portal.git synced 2025-11-15 01:05:49 +00:00
Code Issues Packages Projects Releases Wiki Activity

update content from v1 to v2

Browse Source
This commit is contained in:
Oliver Eggert
2024-11-04 14:17:30 -08:00
parent d093c69ae5
commit 27bcca71a9
20 changed files with 1025 additions and 899 deletions
Download Patch File Download Diff File Expand all files Collapse all files

27
docs/references/http-websocket-apis/public-api-methods/transaction-methods/transaction_entry.md
View File

@@ -76,7 +76,7 @@ An example of a successful response:
"result": {
"ledger_hash": "793E56131D8D4ABFB27FA383BFC44F2978B046E023FF46C588D7E0C874C2472A",
"ledger_index": 56865245,
"metadata": {
"meta": {
"AffectedNodes": [
{
"ModifiedNode": {
@@ -200,7 +200,7 @@ An example of a successful response:
"result": {
"ledger_hash": "793E56131D8D4ABFB27FA383BFC44F2978B046E023FF46C588D7E0C874C2472A",
"ledger_index": 56865245,
"metadata": {
"meta": {
"AffectedNodes": [
{
"ModifiedNode": {
@@ -323,7 +323,7 @@ An example of a successful response:
"result" : {
"ledger_hash" : "793E56131D8D4ABFB27FA383BFC44F2978B046E023FF46C588D7E0C874C2472A",
"ledger_index" : 56865245,
"metadata" : {
"meta" : {
"AffectedNodes" : [
{
"ModifiedNode" : {
@@ -444,6 +444,23 @@ An example of a successful response:
The response follows the [standard format][], with a successful result containing the following fields:
{% tabs %}
{% tab label="API v2" %}
| `Field` | Type | Description |
|:-----------------|:--------------------------|:--------------------------------|
| `close_time_iso` | String | The ledger close time represented in ISO 8601 time format. |
| `hash` | String | The unique hash identifier of the transaction. |
| `ledger_index` | Number - [Ledger Index][] | The ledger index of the ledger version the transaction was found in; this is the same as the one from the request. |
| `ledger_hash` | String - [Hash][] | _(May be omitted)_ The identifying hash of the ledger version the transaction was found in; this is the same as the one from the request. |
| `meta` | Object | The [transaction metadata](../../../protocol/transactions/metadata.md), which shows the exact results of the transaction in detail. |
| `tx_json` | Object | JSON representation of the [Transaction object](../../../protocol/transactions/index.md) |
{% /tab %}
{% tab label="API v1" %}
| `Field` | Type | Description |
|:---------------|:--------------------------|:--------------------------------|
| `ledger_index` | Number - [Ledger Index][] | The ledger index of the ledger version the transaction was found in; this is the same as the one from the request. |
@@ -451,6 +468,10 @@ The response follows the [standard format][], with a successful result containin
| `metadata` | Object | The [transaction metadata](../../../protocol/transactions/metadata.md), which shows the exact results of the transaction in detail. |
| `tx_json` | Object | JSON representation of the [Transaction object](../../../protocol/transactions/index.md) |
{% /tab %}
{% /tabs %}
There are a couple possible reasons the server may fail to find the transaction:
* The transaction does not exist