---
title: "updateActionStatus - Update asynchronous action status"
method: PUT
path: "/v1/orders/actions/{action_id}"
tags: ["Orders"]
---

# updateActionStatus - Update asynchronous action status

`PUT /v1/orders/actions/{action_id}`

<div class="extension-title">Description</div>

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 `action_id` 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


<div class="api-description-extension">
<div class="extension-title">Call Frequency</div>

<div class="recommended-call-frequency">Recommended usage: Send update as soon as the action is completed</div>
<div class="max-call-frequency">Maximum usage: Once per action completion</div>
</div>

## Path parameters

- `action_id` string, required

## Request body

- UpdateActionRequest — Request payload for updating an asynchronous action's status
  - `errors` ActionError[] — List of errors encountered during action processing. Required when status is FAILED. Multiple errors can be included to provide comprehensive failure details.
    - `code` string, required — Machine-readable error code identifying the type of failure. Enum: `"INVALID_INPUT"`, `"DATA_NOT_FOUND"`, `"UNEXPECTED"`, `"UNAVAILABLE"`, `"TOO_MANY_REQUEST"`, `"ACTION_NOT_SUPPORTED"`, `"ORDER_IN_WRONG_STATE"`, `"RETURN_IN_WRONG_STATE"`, `"CARRIER_NOT_SUPPORTED"`, `"MISSING_CARRIER"`, `"WAREHOUSE_ID_NOT_FOUND"`, `"WAREHOUSE_ID_REQUIRED"`, `"OTHER"`
    - `message` string, required — Human-readable description of the error.
  - `status` string, required — The final status of the asynchronous action: * SUCCESS - The action completed successfully with no errors * FAILED - The action encountered errors and could not be completed (requires error details in the errors array) Enum: `"SUCCESS"`, `"FAILED"`

## Response `204`

The action status was successfully updated. No additional content is provided.

## Other responses

- `400` — The request was invalid. Common causes include: - Invalid action status : must be either SUCCESS or FAILED - Action is already in a final state (SUCCESS or FAILED). This error will have code `ACTION_ALREADY_FINAL`. - Invalid error format
- `404` — The specified action ID was not found. This may occur if: - The ID is incorrect - The action has expired - The action was already completed

---

[API](https://skmtc.net/mirakl/apis/mirakl-connect-channel-platform-apis.md) · [All operations](https://skmtc.net/mirakl/apis/mirakl-connect-channel-platform-apis/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/mirakl/mirakl-connect-channel-platform-apis/revisions/7810ddb35640/schema)