# Order Dispatch

The Order Dispatch API updates the status of specified orders to dispatched state, indicating they have been handed over to the delivery partner. If a dispatched event is raised for a canceled shipment, the system will generate an objection.

> **Request Type**: `POST`
**Scheme**: `HTTPS`
**Endpoint**: `https://{{host}}/oms/v3/shipment/dispatch`


Try out Fynd Konnect's Order Dispatch Endpoint
br
**Common Request Header**

| Header | Mandatory | Description |
|  --- | --- | --- |
| `x-access-token` | Yes | The token required for authenticated calls to Fynd Konnect. |


Important Considerations
- Up to 20 order dispatch calls can be sent to Fynd in a single API call


### Body

### Success Response

### API Call Example

## Error Codes

| Reason | Code | Description |
|  --- | --- | --- |
| Cancelled by customer/seller | D401 | If `orderId` is cancelled |
| Invalid `orderId` | D422 | If `orderId` does not belong to the requested location |
| Invalid request | D400 | If dispatch request is raised when the current status is not `packed` |


Next Steps
* Post-dispatch, for channel shipping, merchants can get milestone updates from the Fynd Seller Portal. Partners can fetch in-transit and delivered orders; see [Fetch Orders](/konnect/channels/erp-wms/api-documentation/orders/get-orders)
* For self-ship orders, post-dispatch, update Fynd once the order is handed over to the customer using the [Update Shipment Status](/konnect/channels/erp-wms/api-documentation/orders/put-update-shipment-status) endpoint