`api.deposits.list`

List deposits into the org's virtual accounts, funds that arrived outside of an order. Seismic registers each deposit when it is first reported and advances its status forward as it settles (pending / under_review → completed, or refunded / failed when the funds bounce), so a deposit that never completes is still visible here. The read-side twin of the deposit.status_changed webhook event: each entry's id matches the events' deposit.id, so the surfaces reconcile. Newest first. Optionally filter by account, customer, kind.

const  = await ..();
 
// Deposits into a single virtual account.
const  = await ..({
  : "7c1d2a90…",
});
 
// Fiat deposits across one customer's accounts.
const  = await ..({
  : "2f10…",
  : "fiat",
});

Arguments

Param	Type	Notes
`account_id`	string?	Narrow to a single account.
`customer_id`	string?	Narrow to a single customer.
`kind`	`"fiat"` \| `"crypto"`?	Narrow to one account kind.
`limit`	integer (1–200, default 50)?	Page size.
`cursor`	string?	Opaque cursor from the prior page's `next_cursor`.

Returns: Promise<AccountDeposit[]>. See Deposit fields for the shape. status is the deposit's lifecycle state and status_reason (usually absent) carries the reported explanation for it. received_at is when Seismic registered the deposit, and amount / currency are absent when the deposit report omitted them. transaction_hash is the on-chain settlement hash, present only on crypto-rail deposits. reference is the payment reference reported with the deposit (the bank statement line of the credit) when there was one. source names the sending party (bank routing number, account number, rail) when it was reported.

REST endpoint: GET /deposits.