Ctrl+K

Create Wallet Event

post/api/v2/internal/walletEvents

Create a wallet event in wallet platform

Request Body

type string required
for mmi events, should be 'MMI'
subtype string required
for mmi events, should be 'TRANSACTION', 'BALANCE', or 'ROLLUP'
timeEventOccurred string required
date-time in accordance with https://datatracker.ietf.org/doc/html/rfc3339#section-5.6 representing the time at which the actual mmi transaction occured.
timeEventSent string required
date-time in accordance with https://datatracker.ietf.org/doc/html/rfc3339#section-5.6 representing the time at which the event was sent to wallet platform
source string required
the name of the service sending the event
asset string required
A cryptocurrency or token ticker symbol.
amountDelta string required
Signed number represented as string indicating the quantity of asset leaving (negative) or entering (positive) the address. Zero values indicating no change accepted.
decimals number required
The number of decimals used to represent the amountDelta
marketPrice number required
Nonzero number representing the consensys point in time price for the asset
usersAddress string required
the address sending crypto to or receiving crypto from the defi network
idempotencyKey string required
a hash that can be consistently generated from the same event.
walletId string required
the wallet id with which the transaction takes place
enterpriseId string required
the mongo id of the enterprise that the transaction falls under
txid string required
The on-chain transaction id
txState string required
The state of the transaction on-chain. Can be 'CONFIRMED' or 'REMOVED'

200 Response

id string
object id in mongo
Example: 59cd72485007a239fb00282ed480da1f
Match pattern: ^[0-9a-f]{32}$
timeEventOccurred string
date-time in accordance with https://datatracker.ietf.org/doc/html/rfc3339#section-5.6 representing the time at which the actual mmi transaction occured.
Example: 2022-01-10T17:30:30.000Z
timeEventSent string
date-time in accordance with https://datatracker.ietf.org/doc/html/rfc3339#section-5.6 representing the time at which the event was sent to wallet platform
Example: 2022-01-10T17:31:30.000Z
timeEventReceived string
date-time in accordance with https://datatracker.ietf.org/doc/html/rfc3339#section-5.6 representing the time at which wallet platform received the event
Example: 2022-01-10T17:33:30.000Z
type string
for mmi events, should be 'MMI'
Example: MMI
subtype string
for mmi events, should be 'TRANSACTION', 'BALANCE', or 'ROLLUP'
Example: BALANCE
source string
the name of the service sending the event
Example: indexer
asset string
A cryptocurrency or token ticker symbol.
Example: ETH
decimals number
The number of decimals used to represent the amountDelta
Example: 18
amount string
Signed number represented as string indicating the quantity of asset leaving (negative) or entering (positive) the address
Example: -60000003247
consensysPrice number
Nonzero number representing the consensys point in time price for the asset
address string
the address sending crypto to or receiving crypto from the defi network
Example: 0x71C7656EC7ab88b098defB751B7401B5f6d8976F
idempotencyKey string
a hash that can be consistently generated from the same event.
Example: f28e44259cf048638a293e7850594e39
walletId string
the wallet id with which the transaction takes place
Example: 48dd72485007a239fb00282ed480da1f
enterpriseId string
the mongo id of the enterprise that the transaction falls under
Example: 61b8e0043daafc65a85d4bd36b4649d4
txid string
The on-chain transaction id
Example: b8a828b98dbf32d9fd1875cbace9640ceb8c82626716b4a64203fdc79bb46d26
txState string
The state of the transaction on-chain. Can be 'CONFIRMED' or 'REMOVED'
Example: CONFIRMED

400 Response

error string required
Human-readable error message
requestId string required
Client request id
context object
Properties that apply to a specific error name
name string required
Error code