# updateActionStatus - Update asynchronous action status 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 Endpoint: PUT /v1/orders/actions/{action_id} Security: Bearer ## Path parameters: - `action_id` (string, required) The unique identifier of the action. This ID was provided in the original command event that initiated the action. Example: "1ba5fc4b-c4fd-4251-880b-3052e301bbd4" ## Request fields (application/json): - `errors` (array) List of errors encountered during action processing. Required when status is FAILED. Multiple errors can be included to provide comprehensive failure details. - `errors.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", "OTHER" - `errors.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 400 fields (application/json): - `code` (string, required) Error code (immutable) - `errors` (array) - `errors.extensions` (object) Free map where you find additional context data to better describe the error - `errors.field` (string) JsonPath to the field where the error occurred - `errors.message` (string, required) Literal string error item description (Please do not base your error handling on this field since it is subject to change) - `message` (string, required) Literal string error description (Please do not base your error handling on this field since it is subject to change) ## Response 404 fields (application/json): - `code` (string, required) Error code (immutable) - `errors` (array) - `errors.extensions` (object) Free map where you find additional context data to better describe the error - `errors.field` (string) JsonPath to the field where the error occurred - `errors.message` (string, required) Literal string error item description (Please do not base your error handling on this field since it is subject to change) - `message` (string, required) Literal string error description (Please do not base your error handling on this field since it is subject to change)