Skip to content
This repository has been archived by the owner on Sep 2, 2023. It is now read-only.

Commit

Permalink
Document min_ledger/max_ledger for get transaction request
Browse files Browse the repository at this point in the history
  • Loading branch information
@wltsmrz
wltsmrz committed Apr 13, 2015
1 parent 3144347 commit dd34988
Showing 1 changed file with 7 additions and 0 deletions.
7 changes: 7 additions & 0 deletions README.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -2237,6 +2237,13 @@ The following URL parameters are required by this API endpoint:
|-------|-------|-------------|
| hash | String | A unique identifier for the Ripple transaction to retrieve -- either a client resource ID or a Ripple transaction hash. |
Optionally, you can include the following query parameters to check that the server receiving the request has the full range of ledgers specified. Both are required for range checking.
| Field | Value | Description |
|-------|-------|-------------|
| min_ledger | Number | Lower ledger bound, inclusive |
| max_ledger | Number | Upper ledger bound, inclusive |
#### Response ####
The result is a JSON object, whose `transaction` field has the requested transaction. See the [Transaction format documentation](https://ripple.com/build/transactions) for a complete explanation of the fields of a transaction.
Expand Down

0 comments on commit dd34988

Please sign in to comment.