> ## Documentation Index
> Fetch the complete documentation index at: https://docs.salesbricks.com/llms.txt
> Use this file to discover all available pages before exploring further.

# order.reinstated

> [!TIP]
>
> Make sure to read the [Webhooks Overview](https://docs.salesbricks.com/api-reference/webhooks/overview.md) for important
> information about signature verification.

## Purpose

The `order.reinstated` webhook is triggered when a termination recorded on an **Order** is cancelled, so the order carries on to its original end date.

It is the counterpart of [`order.terminated`](https://docs.salesbricks.com/api-reference/webhooks/order/terminated), and fires whether the termination was still scheduled or had already taken effect. In the payload, `terminated_at` is `null` again.

If the subscription had already gone inactive, reinstating it restores service as long as the order's end date is still ahead (see [`subscription.inactive`](https://docs.salesbricks.com/api-reference/webhooks/subscription/inactive#timing-and-delivery)). A reinstatement after the end date does not restore service.

Each reinstatement sends its own event.

## Payload format

Your configured endpoint will receive an [Order](https://docs.salesbricks.com/api-reference/webhooks/order/payload.md) payload.


## Related topics

- [subscription.inactive](https://docs.salesbricks.com/api-reference/webhooks/subscription/inactive.md)
- [invoice.voided](https://docs.salesbricks.com/api-reference/webhooks/invoice/voided.md)
- [order.complete](https://docs.salesbricks.com/api-reference/webhooks/order/complete.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.