Skip to main content
POST
Record a deposit a user just sent

Body

application/json
chain_id
integer
required

Chain ids are omni's (v2_1.omni.hot.tg), not always the chain's own: EVM chains use their EIP-155 id (Ethereum 1, Optimism 10, BNB 56, Polygon 137, Monad 143, X Layer 196, Base 8453, Arbitrum 42161, Avalanche 43114, ...); the others have omni's numbers: Solana 1001, NEAR 1010, Stellar 1100, TON 1117 (TON v1, 1111, is dead), Juno 4444118, Gonka 4444119.

Required range: x >= 1
Examples:

1100

1117

137

4444119

tx
string
required

The source tx: 32-byte hex (lowercased; 0x kept), or a base58/base64 hash (16–128 characters), kept as given.

Example:

"3b1f6c0e9d2a47c58e6f1a2b3c4d5e6f708192a3b4c5d6e7f8091a2b3c4d5e6f"

intent_account
string
required

A NEAR Intents account: a NEAR account (alice.near, a 64-hex implicit account), an EVM address, or a base58 32-byte key (a Solana address, taken as its hex implicit account).

Examples:

"alice.near"

"0xe4df1d74122c2a7b14481cbdde704fbd0a4f11a2"

Response

The row, or recorded: false without the database.

recorded
boolean
required

False without the database.

deposit_hash
string
required

The account's deposit receiver.

Pattern: ^[1-9A-HJ-NP-Za-km-z]+$
deposit
object

A deposit in the registry. What the client posted is a claim; the relay fills the rest from the chain.