Skip to main content

Confirm Order

Confirm and pay for pending orders.

Endpoint

POST /v1/order/confirm

Request

Header Parameters


ParameterTypeRequiredExampleDescription
AuthorizationstringYesBearer YOUR_ACCESS_TOKENBearer access token used for authentication.
Content-TypestringYesapplication/jsonRequest body content type.

Request Body Schema

application/json
order_idrequired
string
Order ID to confirm.
Must be a valid numeric string.
Example: 3550609

Example Request Body

{
"order_id": "3550609"
}

Example request

curl -X POST "${API_URL}/v1/order/confirm" \
-H "Authorization: Bearer <ACCESS_TOKEN>" \
-H "Content-Type: application/json" \
-d '{"order_id": "3550609"}'

Responses

200 Success

200 Success

Response schema: application/json
data
json-string
Confirmation result.
Expand for fields.
confirmed_orders
array
List of confirmed order objects.
Expand for item fields.
order_id
string
Internal order identifier.
Example: 3550912
ship_type
string
Shipping type (local or intl).
Example: local
order_status
string
Order status after confirmation.
Example: READY_TO_SHIP
Expand for supported values.
Order status codes:
Status CodeDescription
PENDING_CONFIRMOrder awaiting confirmation/payment
READY_TO_SHIPOrder confirmed and ready for pickup
PENDING_PICKUPWaiting for courier pickup
PICKUP_COMPLETEDPicked up by courier
IN_TRANSITPackage in transit
DELIVEREDPackage delivered
COMPLETEDOrder completed
CANCELLEDOrder cancelled
PROCESSINGOrder is being processed (e.g. generating/printing shipping label).
PENDING_PROCESSINGOrder requires manual handling by Fuuffy IT staff. Contact Fuuffy IT for follow-up.
quote_price
string
Quoted shipping price.
Example: 28.50
confirm_shipment
string
Whether shipment is confirmed (Y).
tracking_number
string
Tracking number when available.
Example: SF7444700509270
client_remarks
string | null
Client reference or remarks.
create_time
string
Order creation timestamp (ISO 8601).
Example: 2025-12-09T17:28:55+08:00
message
string
Human-readable status message.
Example: OK

Response sample

{
"data": {
"confirmed_orders": [
{
"order_id": "3550912",
"ship_type": "local",
"order_status": "READY_TO_SHIP",
"quote_price": "28.50",
"confirm_shipment": "Y",
"tracking_number": "SF7444700509270",
"client_remarks": "#5493979",
"create_time": "2025-12-09T17:28:55+08:00"
}
],
"message": "OK"
}
}

Note: Payment is deducted from member balance, a tracking number may be generated upon success for certain courier types.

400 Bad Request

400 Bad Request

Response schema: application/json
error.code
string
Error code.
Example: 400000 or 400211
error.code_reason
string
Error reason (e.g. BAD_REQUEST, NO_ORDERS_FOUND).
error.message
string
Summary of the error.
error.error_trace
json-string
Validation details
field
string
Request field that failed validation.
Example: order_id
message
string
Human-readable explanation.

Response sample

{
"error": {
"code": "400000",
"code_reason": "BAD_REQUEST",
"message": "Bad Request",
"error_trace": {
"order_id": "order_id is required and must be a valid numeric string"
}
}
}

401 Unauthorized

401 Unauthorized

Response schema: application/json
code
string
Error code.
Example: 401000
code_reason
string
Error reason.
Example: UNAUTHORIZED
message
string
Human-readable message.
Example: Unauthorized
{
"error": {
"code": "401000",
"code_reason": "UNAUTHORIZED",
"message": "Unauthorized"
}
}

403 Forbidden

403 Forbidden

Response schema: application/json
error
json-string
Access forbidden for this resource.

404 Not Found

404 Not Found

Response schema: application/json
error
json-string
Resource or endpoint not found.

500 Failure

500 Failure

Response schema: application/json
code
string
Error code.
Example: 500999
code_reason
string
Machine-readable error reason.
Example: API_ERROR
message
string
Human-readable message.
Example: Api Error, please contact customer service
{
"error": {
"code": "500999",
"code_reason": "API_ERROR",
"message": "Api Error, please contact customer service"
}
}