# Webhook Event Types

This page lists the webhook event types MVMNT can send so you can:
- pick the right events when configuring a webhook in MVMNT, and
- route incoming events to the right handler in your system.

Payload shape is the same for every delivery (top-level `sentAt`, plus an `events[]` array). What changes is the `events[].event` value and the event-specific fields inside `events[].data`. See [Webhooks Overview](./overview.md) for the st
andard payload structure.

## Event Categories

### Order Events

#### `order.created`
- **Description**: Order created
- **When you receive it**: When a new order is created in MVMNT
- **Notes**: Use this to kick off downstream workflows that start at order creation

#### `order.updated`
- **Description**: Order updated
- **When you receive it**: When an existing order is updated in MVMNT
- **Notes**: If a change diff is included, it will appear in `events[].diff` (see overview)

#### `order.status_changed`
- **Description**: Order status changed
- **When you receive it**: When an order’s status changes
- **Notes**: Prefer this over `order.updated` when your logic only cares about status transitions

#### `order.deleted`
- **Description**: Order soft-deleted
- **When you receive it**: When an order is soft-deleted in MVMNT
- **Notes**: Treat this as “no longer active” rather than a hard delete

### Shipment Events

#### `shipment.created`
- **Description**: Shipment created
- **When you receive it**: When a new shipment is created in MVMNT
- **Notes**: Useful for syncing shipment creation into your system of record

#### `shipment.updated`
- **Description**: Shipment updated
- **When you receive it**: When an existing shipment is updated in MVMNT
- **Notes**: If a change diff is included, it will appear in `events[].diff` (see overview)

#### `shipment.status_changed`
- **Description**: Shipment status changed
- **When you receive it**: When a shipment’s status changes
- **Notes**: Use this for milestone-driven workflows (e.g., in transit → delivered)

#### `shipment.location_updated`
- **Description**: Tracking location updated
- **When you receive it**: When a shipment’s tracking location is updated
- **Notes**: Use this for map views, ETA refreshes, or exception detection

#### `shipment.delivered`
- **Description**: Shipment delivered
- **When you receive it**: When a shipment is marked delivered
- **Notes**: Often a trigger for POD collection, customer notifications, and billing workflows

#### `shipment.deleted`
- **Description**: Shipment soft-deleted
- **When you receive it**: When a shipment is soft-deleted in MVMNT
- **Notes**: Treat this as “no longer active” rather than a hard delete

### Document Events

#### `document.created`
- **Description**: Document uploaded or generated
- **When you receive it**: When a document is uploaded to or generated by MVMNT
- **Notes**: Use this to pull new docs into your internal storage or notify back-office teams

#### `document.updated`
- **Description**: Document metadata updated
- **When you receive it**: When a document’s metadata changes
- **Notes**: Useful if you mirror document tags/types/status in another system

#### `document.deleted`
- **Description**: Document soft-deleted
- **When you receive it**: When a document is soft-deleted in MVMNT
- **Notes**: Treat this as “removed from active use” rather than a hard delete

### Carrier Events

#### `carrier.tender_sent`
- **Description**: Tender sent to carrier
- **When you receive it**: When a tender is sent to a carrier
- **Notes**: Use this to track tender lifecycle and automate follow-ups

#### `carrier.tender_accepted`
- **Description**: Carrier accepted tender
- **When you receive it**: When a carrier accepts a tender
- **Notes**: Common trigger for confirmation workflows and downstream scheduling

#### `carrier.tender_rejected`
- **Description**: Carrier rejected tender
- **When you receive it**: When a carrier rejects a tender
- **Notes**: Common trigger for coverage workflows (retry, re-tender, escalate)

More event types will be added as entity specifications are documented.

See [Webhooks Overview](./overview.md) for webhook basics.