Transaction Notification

After the address has been deposited or the transaction initiated actively is put on the chain, a notification will be pushed. For callback rules, please refer to the relevant instructions in MPC WaaS Quick Start.

application/json

Request Body

requestType integer required

Callback request type (0-withdrawal; 1-deposit)

requestId string required

The unique ID of the request, unchanged after multiple calls

requestDetail object required
Detailed information of the callback request; the format is serialized JSON string, currently containing the following parameter content
sinoId string
Transaction serial number, will be returned when transferring, fixed as 0 for deposits
txHash string required
Transaction hash, on-chain data
confirmNumber integer required
Confirmation number, currently fixed to 0
walletId string
wallet id
chainSymbol string required
Unique identification of the chain
assetId string required
Unique asset identifier
txDirection integer required
Transaction type：0-withdrawal; 1-deposit
note string
Fill in the value when creating a withdrawal transaction; not applicable for deposit transactions
nonce integer
EVM compatible chain transaction nonce value, returned when the transaction type is 0 (withdrawal); returned as 0 when the transaction type is 1 (deposit)
from string required
from address
to string required
to address
toTag string
Value provided during withdrawal transaction creation; null for deposit transactions
amount string required
Amount
decimal integer required
Precision
fee string required
For withdrawal transactions, the fee determined when constructing the transaction
feeAsset string required
Fee token identification
feeAssetDecimal integer required
Fee token only precision
usedFee string required
Actual usage fee
gasPrice string
ethlike will have a value, non-ethlike will be given 0.
gasLimit string
ethlike will have a value, non-ethlike will be given 0.
state integer required
10 - The transaction was successfully uploaded to the chain; 5 - The actively initiated (contract interaction type transaction) has been uploaded to the chain, but the on-chain execution status is failed; 4 - failure before on-chain, such as sign callback reject
brc20Details object[]
交易记录列表
Array [
method string
operation type
ticker string
inscription name
quantity string
the number of this operation
inscriptionId string
inscription id
step int
1:commit 2:reveal 3:transfer
from string
from address
to string
to address
]
runeDetails object[]
Array [
fromAddress string
toAddress string
runeName string
runeId string
runeSpacedName string
runeSymbol string
runeDivisibility int
]
extraInfo string

Other information related to the callback request; there is currently no clear information

Responses

• 200

---

successful operation

application/json

Schema

Example (from schema)

---

Schema

code integer
requestId string

The unique ID of the request, unchanged after multiple calls

message string

Error message

{
  "code": 200,
  "requestId": "431431431431431",
  "message": ""
}

Loading...