Skip to main content
transactionHash
string
required
Maximum string length: 255
Pattern: ^(?=\S)[\p{L}\p{N}a-zA-Z _.,:!?&%@\/+\-'|]+(?<=\S)$
Example:

"An example name"

blockNumber
number
required

Block number of the transaction

transactionTimestamp
string<date-time>
required

Timestamp of the transaction

blockHash
string
required
Maximum string length: 255
Pattern: ^(?=\S)[\p{L}\p{N}a-zA-Z _.,:!?&%@\/+\-'|]+(?<=\S)$
Example:

"An example name"

blockExplorerUrls
string[]
required

URLs to the block explorer for the transaction

fromAddress
string
required
Maximum string length: 255
Pattern: ^(?=\S)[\p{L}\p{N}a-zA-Z _.,:!?&%@\/+\-'|]+(?<=\S)$
Example:

"An example name"

toAddress
string
required
Maximum string length: 255
Pattern: ^(?=\S)[\p{L}\p{N}a-zA-Z _.,:!?&%@\/+\-'|]+(?<=\S)$
Example:

"An example name"

labels
enum<string>[]
required

A transaction label. sent, received, and swap describe the transaction's direction relative to the wallet. token, external, and internal are asset-category labels emitted for EVM activity; an EVM event's labels array can contain both a category and a direction label.

Available options:
sent,
received,
swap,
token,
external,
internal
assetTransfers
object[]
required
chainName
enum<string>
required
Available options:
ETH,
EVM,
FLOW,
SOL,
ALGO,
STARK,
COSMOS,
BTC,
ECLIPSE,
SUI,
SPARK,
TRON,
APTOS,
TON,
STELLAR
networkId
number
required
Example:

1

memo
string

The UTF-8 text recorded by the transaction's SPL Memo program instruction, when present. Solana only; omitted otherwise.

Example:

"invoice:INV-1042"

registeredAddress
string

The wallet address whose registration triggered this delivery. When one transaction involves several wallets within your environment, you receive one event per wallet, so use networkId, transactionHash, and registeredAddress together to identify each delivery.

Example:

"0xc0d70ec4bf711836207ae61358d5e822111cfdf8"

Other registered wallet addresses in the same environment that also appear in this transaction, grouped by user. External wallets registered without a user are grouped together in an entry that has no userId. These addresses are context only; each one triggers its own event. Empty when no other registered wallet in the environment is involved.

Last modified on January 21, 2026