get transaction hashes by payment id: Difference between revisions

From Talleo Wiki
Jump to navigation Jump to search
No edit summary
(Add startIndex, endIndex and includeUnconfirmed parameters.)
 
(3 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{DISPLAYTITLE:get_transaction_hashes_by_payment_id}}
== Input ==
== Input ==
{| class="wikitable"
{| class="wikitable"
Line 4: Line 5:
|-
|-
| paymentId || yes || Payment ID || [[Hash]]  
| paymentId || yes || Payment ID || [[Hash]]  
|-
| startIndex || false || First block index to include || uint32
|-
| endIndex || false || Last block index to include || uint32
|-
| includeUnconfirmed || false || Include unconfirmed transactions || bool
|}
|}


Line 16: Line 23:


== Description ==
== Description ==
* This is JSON version of [[get_transaction_hashes_by_payment_id.bin]] and uses same structs as the binary version. This means some values need to be converted if passed to methods expecting strings instead of arrays of 8-bit integers.
* This is JSON version of [[get_transaction_hashes_by_payment_id.bin]]. Unlike the binary version, this version allows filtering results by block index and if the transaction is unconfirmed or not.
 
== Notes ==
* Payment ID is passed as array of 8-bit integers, instead of hexadecimal string
* Transaction hashes are returned as array of 8-bit integers, instead of hexadecimal string

Latest revision as of 12:30, 3 April 2020

Input

Argument Mandatory Description Format
paymentId yes Payment ID Hash
startIndex false First block index to include uint32
endIndex false Last block index to include uint32
includeUnconfirmed false Include unconfirmed transactions bool

Output

Argument Description Format
transactionHashes List of transaction hashes array
status Status of request, "OK" if successful string

Description