Transaction
Last updated
Was this helpful?
Last updated
Was this helpful?
The APIs related to executing transactions consist of three components:
/v1/tx/prepare
/v1/tx/sign
/v1/tx/broadcast
The necessary APIs can be executed sequentially depending on the situation
Generating a signature only: Retrieve Transaction Information ⇒ Sign Transaction
Generating a signature and broadcasting in a single step: Retrieve Transaction Information ⇒ Broadcast Transaction
(Optional) Generating a signature and broadcasting: Retrieve Transaction Information ⇒ Sign Transaction ⇒ Broadcast Transaction
Retrieve information such as the required transaction fee.
Parameter
userId
String
O
accountId
String
Account ID to send from /v1/account response value.
O
contract
String
Contract address of the token to be sent when sending tokens.
X
to
String
Recipient address
O
isNft
String
ERC1155 | ERC721
Define NFT scheme type when transferring FT.
X
tokenId
Number String
NFT token ID when isNft is set and transferring an NFT.
X
amount
String
Amount of coin or token to send when transferring FT.
X
Success Response
balance
String
The current balance of the account to be transferred.
decimals
String
The decimals of the coin in the account to be transferred.
symbol
String
The symbol of the coin in the account to be transferred.
tokenId
Number
If the account to be transferred is a token account, the tokenId.
detail
TxData(Object)
The data required for the transaction. The TxData format differs depending on the type of account.
Parameter
userId
String
O
type
String
Types of Signatures
•transaction (transaction) | msg_sign (Personal sign) | sign_data (typed data)
• The configuration of txData differs depending on the type.
•msg_sign | sign_data currently supports only EVM transactions.
O
pin
UVD
User's UVD
O
walletId
String
User Wallet ID
O
accountId
String
O
tokenId
String
tokenId for token transfers.
X
isNft
String
ERC1155 | ERC721
X
contract
String
Contract address for token transfers.
X
txData
TxData(Object)
O
otpCode
Object
OTP authentication information.
X
Success Response
signatureResult
Object
Sign result value. Structure varies by transmission network.
transaction
Object
Transmission details.
Sends the signed transaction.
Parameter
userId
String
O
type
String
Types of Signatures
• transaction (transaction) | msg_sign (Personal sign) | sign_data (typed dat
• The configuration of txData varies depending on the type.
• msg_sign | sign_data currently supports only EVM transactions.
O
pin
UVD
User's UVD
O
walletId
String
User Wallet ID
O
accountId
String
O
tokenId
String
tokenId for token transfers.
X
contract
String
Contract address for token transfers.
X
isNft
String
ERC1155 | ERC721
X
signatureResult
String | Object
When executing in the order of /prepare, /sign, and /broadcast, this is the already signed data to be broadcasted. Use the data received after signing (/tx/sign) without modification.
X
txData
TxData(Object)
X
otpCode
Object
OTP authentication information.
X
Success Response
signatureResult
Object
Sign result value. The structure varies slightly depending on the transmission network.
transaction
Object
Transmission details.
broadcastData
String
Data sent to the network.
txid
String
Transaction ID
userId from the response.
The actual signing is performed using the data obtained through . If necessary, the fee value in TxData can be modified before signing. Before signing, the user's wallet PIN must be obtained using the PIN Pad Library, and the UVD must be sent together.
userId from the response.
ID of the account to be sent. Must match the accountId from .
Transaction data required. Includes the data values retrieved through , with a format differing based on the type of account.
userId from the response.
ID of the account to be sent. Must match the accountId from
When executing in the order of /prepare and /broadcast, this is the required transaction data when signing and broadcasting in a single process. Transaction data required. Includes the data retrieved through , with a format differing based on the type of account.