Skip to main content
Portal calls your server in two different ways. Flow control hooks pause a wallet operation until your server answers, and your answer decides what happens next. Informational webhooks tell your server that something already happened, and nothing waits on your response. Each kind has its own page in the Portal Admin Dashboard, under Webhooks in the sidebar: Flow control and Informational.

​
Compare the two kinds

​
Which one do I need?

Use flow control hooks if you need to:
  • Approve or reject every signature before it happens, for example to enforce your own transaction limits.
  • Store your clients’ custodian backup shares in your own infrastructure instead of using Portal-managed backups.
Use informational webhooks if you need to:
  • Track deposits, withdrawals, token approvals, and revocations on your clients’ EVM and Solana wallets.
  • Keep your records in sync when a client creates, backs up, recovers, or ejects a wallet.
You can configure both. Each environment has at most one flow control configuration and one informational webhook.
If your environment uses Portal-managed backups, the dashboard hides the /backup and /backup/fetch hooks, and signature approvals are the only flow control hook available.

​
Get started

Flow control hooks

Response contracts for signature approvals and self-managed backups.

Informational webhooks

Delivery, retries, deduplication, and the event log.

Set up flow control hooks

Walk through the flow control wizard in the dashboard.

Set up informational webhooks

Walk through the informational wizard in the dashboard.
Integration webhooks (Due, Noah, Meld) are documented on each integration’s page.