The following functionality exists for wallets reconstituted
server-side. More on Privy architecture
here
Webhooks is currently a scale feature. To use webhooks, please upgrade your account in the Privy
Dashboard.
Deposit webhooks are available for Tier 3 chains and select Tier 2 chains.
Setup a webhooks URL
To start, go to the Webhooks page for your app in the Privy Dashboard and provide a destination URL for receiving webhooks. Then, enable the'wallet.funds_deposited'
and/or 'wallet.funds_withdrawn'
events. You can next configure which assets Privy should emit 'wallet.funds_deposited'
and/or 'wallet.funds_withdrawn'
events for.
Privy will emit a signed webhook to this URL whenever your wallets sends/receives a transaction for a registered asset, and will retry delivery if the endpoint does not successfully respond to the original webhook.
Privy’s webhook system operates on a at least once
delivery basis, and redundant requests can be identified via the idempotency_key
field.
Configure assets to track
Once you’ve enabled the'wallet.funds_deposited'
and/or 'wallet.funds_withdrawn'
events, you can then configure which assets you’d like to track via the Privy Dashboard.
Privy supports webhooks for native tokens (e.g. ETH, SOL) on EVM and Solana, ERC20 tokens on EVM, and SPL tokens on Solana.
Native tokens
To configure webhooks for native token transactions, simply select the Native token asset type and provide the CAIP-2 chain ID for the network on which to track the native token.ERC20 tokens
To configure webhooks for ERC20 token transfers, simply select the ERC20 token asset type and provide:- the contract address for the ERC20 token
- the CAIP-2 chain ID for the network on which to track the ERC20 token
SPL tokens
To configure webhooks for SPL token transfers, simply select the SPL token asset type and provide:- the mint address for the SPL token
- the CAIP-2 chain ID for the network on which to track the SPL token