# Webhooks

Digital River uses webhooks to notify your application when events occur.

When an event occurs, Digital River will create an [Event](https://app.gitbook.com/s/x8fSFzVR3sg0TsNWwwVz/events) object and then send a webhook to your application (endpoint URL) through a `POST` request containing the event and a timestamp. You can set up multiple webhook endpoints to receive a single event. This allows you to receive real-time updates on the state of your SKUs, orders, fulfillments, returns, and refunds.

The Webhook resource can take specific actions when events occur. For example, you can expect to receive a `checkout.created` event when a customer begins the checkout process. An `order.accepted` event signals that the order is [ready to fulfill](https://docs.digitalriver.com/digital-river-api/order-management/fulfillments) and a `fulfillment.created` event indicates an invoice is generated.

Webhook endpoints can be better secured by using a signing secret and authenticating via [OAuth](https://docs.digitalriver.com/digital-river-api/order-management/events-and-webhooks-1/creating-a-webhook#oauth-transport-type) or [basic authorization](https://docs.digitalriver.com/digital-river-api/order-management/events-and-webhooks-1/creating-a-webhook#http-transport-type).

You can send webhooks to your customer that include this tracking information, [create a webhook](https://docs.digitalriver.com/digital-river-api/order-management/events-and-webhooks-1/webhooks/creating-a-webhook) to subscribe to the event, and share a file link with the customer without using a secret key when you receive the webhook.