Metaplex Umi has no getSignaturesForAddress or getParsedTransactions — use umi.rpc.call, or reach the underlying web3.js Connection

Situation: you migrated a script to Metaplex Umi and need transaction history for an address (an ATA, a PDA, a proceeds account). The methods you used on web3.js Connection — getSignaturesForAddress, getParsedTransactions — do not exist on umi.rpc, and Umi's RpcInterface exposes no equivalent.

Umi's RPC interface deliberately covers only the subset of methods its programs need, so history queries are missing rather than renamed. Two escape hatches:

1. The generic pass-through. umi.rpc.call sends an arbitrary JSON-RPC method with a positional parameter array, so anything the node supports is reachable:

const signatures = await umi.rpc.call("getSignaturesForAddress", [proceedsAddress]);

You get the raw JSON-RPC shape back — no Umi types, no camel-cased wrappers — so type the result yourself.

2. Borrow the underlying client. The bundled RPC implementation wraps a web3.js Connection, which you can reach with a cast:

const { connection } = umi.rpc as unknown as { connection: Connection };
await connection.getSignaturesForAddress(proceedsAddress);

Non-obvious parts: nothing in the type definitions hints that umi.rpc.call exists as a fallback, so the usual reaction is to instantiate a second Connection alongside Umi and drift out of sync on endpoints and commitment. Option 2 depends on an implementation detail — it holds for umi-rpc-web3js/umi-bundle-defaults, but a different RpcInterface implementation would have no connection field, so prefer umi.rpc.call for anything long-lived. Also remember Umi passes addresses as its own string-based PublicKey type; umi.rpc.call wants whatever the JSON-RPC method wants, i.e. a base58 string.

Source: adapted from a Stack Exchange answer by Loris Leiva (question by Hyetigran), https://solana.stackexchange.com/questions/9421/how-to-fetch-all-signatures-for-a-given-ata-using-umi-provider-with-mpl-toolbox — CC BY-SA 4.0