# Orders

## updateActionStatus - Update asynchronous action status

 - [PUT /v1/orders/actions/{action_id}](https://developer.mirakl.com/content/product/connect-channel-platform/rest/connect/openapi3/orders/updateactionstatus.md): Updates the final status of an asynchronous action previously initiated through a command event.

## Overview
- When an asynchronous action is requested via command event, an  is provided to track the action
- Use this endpoint to report the final outcome (SUCCESS or FAILURE) of the action
- For failed actions, detailed error information must be provided

## Usage Notes
- Update should be sent once the action is fully completed
- Multiple errors can be provided for failed actions
- The action ID must match the one provided in the original command event
Call FrequencyRecommended usage: Send update as soon as the action is completedMaximum usage: Once per action completion

## updateAnonymizeAfterDate - Update anonymization date for orders

 - [PUT /v1/orders/anonymize-after](https://developer.mirakl.com/content/product/connect-channel-platform/rest/connect/openapi3/orders/updateanonymizeafterdate.md): Updates the anonymization date for orders in the Mirakl Connect platform.
Use this API to indicated after which date orders should be anonymized by Connect.
The anonymization process is irreversible and should be used with caution.
Call FrequencyRecommended usage: Once per order when the anonymization date is setMaximum usage: Every time the anonymization date needs to be changed

## upsertOrders - Upsert orders

 - [POST /v1/orders](https://developer.mirakl.com/content/product/connect-channel-platform/rest/connect/openapi3/orders/upsertorders.md): Use this API to synchronize orders with Mirakl Connect. This API does not support PATCH operations. All fields must be sent with each upsert request to ensure the complete update of the order data.