Get Deposit Detail (V2)
GET
/open-api/v2/wallet/deposit/detailThis method allows you to get the deposit details of the requested transaction ID.
- either txId or orderViewId shall be passed in params
API Key permission group : Enable Enquiry
Request
Query Params
timestamp
integer
required
Current Timestamp in millisecond
Example:
1640995200000
txId
string
optional
Transaction id
Example:
2B2F4DA3D3838D56E90D06D1879B0ABFABD0D45FC4CFEFC6560289E6572F019
orderViewId
string
optional
Order view id
Example:
20372107512956096512
memo
string
optional
Only when memo is necessary for network
Example:
12314
address
string
optional
Address
Example:
inj15jy9vzmyy63ql9y6dvned2kdat2994x5f4ldu4
Header Params
open-apikey
string
required
API key
signature
string
required
Signature of the request
Request samples
Responses
The operation succeeded(200)
Business error(200)
The client request is invalid(400)
Authentication failed (e.g., invalid token specified by the Authorization header)(401)
Authentication failed, but the operation is not allowed(403)
Requested resource does not exist(404)
Client request rate exceeded the limit(429)
System error(500)
The operation succeeded
HTTP Code: 200
Content Type : JSONapplication/json
Data Schema
data
array[object (Transaction) {20}] | null
optional
response data, maybe null
orderViewId
string
required
txId
string | null
optional
transaction id (Only Applicable to on-chain transfer)
transferType
optional
direction
enum<integer>
required
Allowed values:
1020
fromAddress
string
required
toAddress
string
required
network
string | null
optional
coinSymbol
string
required
amount
string
required
feeSymbol
string | null
optional
feeAmount
string | null
optional
status
enum<integer>
required
Allowed values:
1020304099
confirmedBlockCount
integer | null
optional
unlockConfirm
integer | null
optional
maxConfirmBlock
integer | null
optional
currentBlock
integer | null
optional
memo
string | null
optional
txTime
integer | null
optional
walletId
integer
required
requestId
string | null
optional
universal unique identifier provided by the client side.
code
string
required
'000000' indicates success, while any others indicate failure.
message
string
required
When the code is '000000' (success), it represents the details of the response. Otherwise, it represents the details of the error.
Example
{
"data": [
{
"orderViewId": "10369165164303552512",
"txId": "0x1c5b79cfe30b978b053b7bc26f4716378667d49c7edf6c46ae421d256e29c970",
"transferType": 10,
"direction": 10,
"fromAddress": "0xf637e2d5dc3c33655a906d97f6c79d1e33bcfc34",
"toAddress": "0xc8dAe5eb08fe1981D212cFc3744b237e72a99878",
"network": "BSC",
"coinSymbol": "BNB",
"amount": "1.00000000000000000000",
"feeSymbol": "BNB",
"feeAmount": null,
"status": 40,
"confirmedBlockCount": 15,
"unlockConfirm": 15,
"maxConfirmBlock": 15,
"currentBlock": 15,
"memo": null,
"txTime": 1713146204000,
"walletId": 327282886560800800,
"requestId": null
}
],
"code": "000000",
"message": "Success"
}
Last modified: 12 days ago