
Footprint uses webhooks to asynchronously update your application's code on critical events in the lifecycle of an onboarding. Webhooks are critical controls for automating account opening processes and ensuring your user accounts remain in compliance. For example: receive webhooks when a user completes an onboarding, if the status of an onboarding changes when user is verified from a manual review state, or if a OFAC/PEP watchlist alert is triggered for a user.

You can quickly configure webhooks and test them from within the Footprint developer dashboard.

<img
  alt="Webhooks tab"
  height={250}
  src="/webhooks/developer_tab.png"
  width={720}
/>

## Interactive portal

From the [webhooks tab](https://dashboard.onefootprint.com/developers?tab=webhook) in the Footprint developer dashboard you can configure endpoints, test endpoints with sample events, view statistics and logs, and create your signing secret for verification.

<img
  alt="Webhooks example"
  src="/webhooks/example.png"
  height={250}
  width={720}
/>

## Guides and Resources

Below, please find some links guides for consuming Footprint webhooks.

1. [Footprint Webhook Event Types](https://www.svix.com/event-types/us/org_2LbAthqjvv71cc7eYpwvHoeuuEw/)
2. [Guide to consuming webhooks](https://docs.svix.com/receiving/introduction)
3. [Securely verify webhook signatures](https://docs.svix.com/receiving/verifying-payloads/how)
