Get Transaction Request Details
Through this endpoint customers can obtain details on transaction request.
Path Parameters
-
RequiredtransactionRequestId string
Represents the unique ID of the transaction request.
Query parameters
-
Optionalcontext string
In batch situations the user can use the context to correlate responses with requests. This property is present regardless of whether the response was successful or returned as an error.
context
is specified by the user.
Response schema
Content-Type: application/json
The request has been successful.
Object :
-
RequiredapiVersion string
Specifies the version of the API that incorporates this endpoint.
Example : 2021-03-20 -
RequiredrequestId string
Defines the ID of the request. The
requestId
is generated by Crypto APIs and it's unique for every request.Example : 601c1710034ed6d407996b30 -
Optionalcontext string
In batch situations the user can use the context to correlate responses with requests. This property is present regardless of whether the response was successful or returned as an error.
context
is specified by the user.Example : yourExampleString -
Requireddata object
-
Requireditem object
-
RequiredadditionalDetails string
Defines an optional note for additional details.
Example : yourExampleStringHere -
Requiredblockchain string
Represents the specific blockchain protocol name, e.g. Ethereum, Bitcoin, etc.
Example : bitcoin -
RequiredfeePriority string
Defines the priority for the fee, if it is "slow", "standard" or "fast".
Example : standard -
Requirednetwork string
Represents the name of the blockchain network used; blockchain networks are usually identical as technology and software, but they differ in data, e.g. - "mainnet" is the live network with actual data while networks like "testnet", "ropsten" are test networks.
Example : testnet -
Requiredrecipients array
Represents a list of recipient addresses with the respective amounts. In account-based protocols like Ethereum there is only one address in this list.
-
Requiredaddress string
The address which receives this transaction. In UTXO-based protocols like Bitcoin there could be several senders while in account-based protocols like Ethereum there is always only one recipient.
Example : mr3zKBc7skyDHcVHWww4JzzziPnrdYTscR -
OptionaladdressTag integer
Defines a specific Tag that is an additional XRP address feature. It helps identify a transaction recipient beyond a wallet address. The tag that was encoded into the x-Address along with the Classic Address.
Example : 3999472835 -
Requiredamount string
Represents the amount received to this address.
Example : 0.001 -
OptionalclassicAddress string
Represents the public address, which is a compressed and shortened form of a public key. A classic address is shown when the destination address is an x-Address.
Example : rA9bXGJcXvZKaWofrRphdJsBWzhyCfH3z -
Requiredunit string
Defines the unit of the amount.
Example : BTC
-
-
RequiredtotalTransactionAmount string
Defines the total transaction amount.
Example : 0.001 -
OptionaltransactionId string
Represents the unique identifier of a transaction, i.e. it could be transactionId in UTXO-based protocols like Bitcoin, and transaction hash in Ethereum blockchain.
Example : 61922aa68f192800067a8404 -
RequiredtransactionRequestStatus string
Defines the status of the transaction request, e.g. pending.
Example : created -
RequiredtransactionType string
Defines the transaction type, if it is for coins or tokens.
Example : coin -
Requiredunit string
Defines the unit of the amount.
Example : BTC -
RequiredwalletId string
Defines the unique ID of the Wallet.
Example : 60c9d9921c38030006675ff6
-
-