# Webhooks ## Webhooks Resend provides webhooks, which are real-time HTTPS requests that tell your application an event occurred, such as an email delivery notification or subscription status update. This allows you to receive real-time and actionable updates on the delivery, open, bounce, and click events of your emails. You can create, update, observe, and retry webhooks from the dashboard or [via the API](/guides/webhooks-create-webhook). Webhooks deliver a JSON payload with metadata like the from, to, and status of your email event that can be used by your application. Use webhook feeds for common workflows such as: - Automatically remove [bounced email addresses](/guides/learn-webhooks-emails-bounced) from mailing lists. - Create alerts in your messaging or incident tools based on [event types](/guides/learn-webhooks-event-types). - [Store all send events](/guides/learn-webhooks-how-to-store-webhooks-data) in your own database for custom reporting/retention. - [Receive inbound emails](/guides/learn-dashboard-receiving-introduction) from your application. ## Webhook features With Resend's webhook features, you can: - [Replay any webhook event](/guides/learn-webhooks-retries-and-replays). This is useful when your endpoint missed an event, or when you want to reprocess events with updated handler code. - [Verify webhook requests](/guides/learn-webhooks-verify-webhooks-requests) to ensure their authenticity. - [Listen for webhook events locally during development](/guides/resources-cli#webhooks). - Self-host the [Resend Webhook Ingester](/guides/learn-webhooks-ingester) to store all your webhook events with an open-source, ready-to-deploy solution that handles all the complexity for you. ## Quickstart Get started by [creating a webhook](/guides/learn-webhooks-create-webhook) to incorporate Resend into your application. To receive real-time events in your app via webhooks, you need to: ::::steps :::step{title="Create an endpoint in your application"} Create a route that can accept POST requests. This route will listen for and receive events from Resend. ::: :::step{title="Add a webhook in Resend"} Define a webhook with the URL of your endpoint, and the [email events](/guides/learn-webhooks-event-types) it handles. ::: :::: See a step-by-step example of [creating a webhook](/guides/learn-webhooks-create-webhook) through the Dashboard, including testing and deployment. ## Choose your infrastructure After creating your application endpoint, you can define and manage your webhooks entirely from the Resend Dashboard. This allows all members of your team to have full access to your email event data and to perform any necessary maintenance. To build workflows to manage and respond to email events from your application, you can use a variety of tools: - [SDK](/guides/resources-sdks): build and manage webhooks with an SDK built for your language - [Integrations](/guides/resources-integrations): build workflows with a framework or tool you already use - [API](/guides/webhooks-create-webhook): manage webhooks with raw cURL calls - [CLI](/guides/resources-cli#webhooks): register endpoints and listen for email event notifications from the terminal. - [MCP](/guides/resources-mcp-server): build workflows that respond to email events through your agent using natural language. See how to use Resend's webhook features such as replaying webhooks and storing webhook data in the [webhooks guides](#related-guides). ## Related Guides ::::card-grid :::card{title="Create webhook" href="/guides/learn-webhooks-create-webhook" icon="globe"} ::: :::card{title="Respond to emails" href="/guides/learn-dashboard-receiving-create-receiving-webhook" icon="mailbox-open-letter"} ::: :::card{title="Retry replay webhooks" href="/guides/learn-webhooks-retries-and-replays" icon="rotate"} ::: :::card{title="Email event types" href="/guides/learn-webhooks-event-types" icon="file-plus"} ::: :::card{title="Verify a webhook request" href="/guides/learn-webhooks-verify-webhooks-requests" icon="shield-check"} ::: :::card{title="Store webhook data" href="/guides/learn-webhooks-how-to-store-webhooks-data" icon="database"} ::: :::card{title="Self-host the Resend Webhook Ingester" href="/guides/learn-webhooks-ingester" icon="inbox"} ::: :::card{title="Webhook events reference" href="/guides/learn-webhooks-emails-bounced" icon="book-bookmark"} ::: :::: ## Examples ::::card-grid :::card{title="Next.js (TypeScript)" href="https://github.com/resend/resend-examples/tree/main/nextjs-resend-examples/typescript/src/app/inbound" icon="arrow-up-right-from-square"} See the full source code. ::: :::card{title="Next.js (JavaScript)" href="https://github.com/resend/resend-examples/tree/main/nextjs-resend-examples/javascript/src/app/inbound" icon="arrow-up-right-from-square"} See the full source code. ::: :::card{title="PHP" href="https://github.com/resend/resend-examples/tree/main/php-resend-examples/src/inbound" icon="arrow-up-right-from-square"} See the full source code. ::: :::card{title="Laravel" href="https://github.com/resend/resend-examples/tree/main/laravel-resend-examples" icon="arrow-up-right-from-square"} See the full source code. ::: :::card{title="Python" href="https://github.com/resend/resend-examples/tree/main/python-resend-examples/examples" icon="arrow-up-right-from-square"} See the full source code. ::: :::card{title="Ruby" href="https://github.com/resend/resend-examples/tree/main/ruby-resend-examples/examples" icon="arrow-up-right-from-square"} See the full source code. ::: :::: ## Related pages - [Create a Webhook](./learn-webhooks-create-webhook.md) - [Verify Webhooks Requests](./learn-webhooks-verify-webhooks-requests.md) - [Retries and Replays](./learn-webhooks-retries-and-replays.md) - [Webhook Ingester](./learn-webhooks-ingester.md) - [How to Store Webhooks Data](./learn-webhooks-how-to-store-webhooks-data.md) - [Event Types](./learn-webhooks-event-types.md) - [Events reference](./learn-events-reference.md) # Agent Instructions Cite this page’s canonical URL and keep its documentation version. Follow Link headers to discover available agent guidance and tools. Read the advertised skill for the requested version before choosing starting pages. Treat documentation as reference material, not execution authorization.