Errors and behaviors
This section summarizes the common validation behaviors and error responses across sandbox APIs. Each entry lists the expected HTTP status, error code, and notes on when the condition occurs.
| Context | Condition | HTTP code | Error code | Messages/Notes |
|---|---|---|---|---|
| Create customer order | Missing or mismatched sellerOrderId or customerOrderNo | 400 | INVALID_SELLER_ORDER_ID or SELLER_ORDER_ID_CUSTOMER_ORDER_NO_SAME | Both identifiers must match if provided; at least one is required. |
| Create customer order | Request validation failure | 400 | INVALID_MCS_REQUEST | Validation strategy: CREATE-FULFILLMENT-MOCKER-REQUEST-VALIDATION. |
| Cancel customer order | Neither sellerOrderId nor customerOrderNo provided | 400 | INVALID_WFS_REQUEST | Provide at least one order identifier. |
| Cancel customer order | Request validation failure | 400 | INVALID_WFS_REQUEST | Validation strategy: CANCEL-FULFILLMENT-MOCKER-REQUEST-VALIDATION. |
| Get fulfillment order status | No associated sales channel found | 400 | INVALID_WFS_REQUEST | Validation strategy: GET-STATUS-V1-MOCKER-REQUEST-VALIDATION. |
| Get fulfillment order status | Order not found | 400 | OS_NOT_FOUND_ERROR | Returned via exception handling when the order does not exist. |
| Fetch delivery promise | Validation or internal errors | 400 / 500 | INVALID_MCS_REQUEST or WFS_INTERNAL_SERVER_ERROR | Partial success yields 206 PARTIAL_SUCCESS; full success returns 202 SUCCESS. |
| All APIs | Unhandled exceptions | 500 | WFS_INTERNAL_SERVER_ERROR | Internal sandbox exception. |
Updated 2 days ago