Skip to content

Order Status Callback ​

When an order status changes to "Pending Delivery" (sellerOrderStatus = 1), meaning the order has been paid and passed risk review, the platform pushes a notification to the seller's configured callback URL.

Basic Information ​

PropertyValue
MethodPOST (platform pushes to seller)
Path{seller_callback_url}
VerificationHMAC-SHA256 Signature
Content-Typeapplication/json

Request Headers ​

The platform passes signature-related fields via HTTP headers:

HeaderTypeRequiredDescription
Content-TypestringYesAlways application/json
X-Request-IdstringYesUnique identifier for this callback request, used for idempotency
X-TimestampstringYesUnix millisecond timestamp (e.g., 1734850099000)
X-SignaturestringYesHMAC-SHA256 signature value

Request Body ​

json
{
  "createdAt": "2025-12-17T13:44:16",
  "orderId": 1689644928115784,
  "orderNum": "SO1689644928115784",
  "sellerOrderStatus": 1,
  "buyerId": "1907369850568257537"
}

Field Descriptions ​

FieldTypeDescription
createdAtstringOrder creation time (ISO 8601 format)
orderIdnumberUnique order ID
orderNumstringOrder number
sellerOrderStatusnumberSeller-side order status (see Status Codes)
buyerIdstringBuyer user ID

Processing Flow ​

After receiving a callback, follow these steps:

1. Verify Signature ​

Extract X-Timestamp, X-Request-Id, and X-Signature from the request headers. Verify the request authenticity using the Signature Verification algorithm.

2. Idempotency Check ​

Check whether the X-Request-Id has already been processed. If it is a duplicate request, return HTTP 200 immediately.

3. Query Order Details ​

Use the orderId from the callback to call the Order Query API to retrieve full order details (product information, quantity, buyer delivery requirements, etc.).

4. Execute Business Logic ​

Prepare the delivery based on the order details. Once ready, call the Deliver Order API to submit the delivery information.

5. Return Success ​

Return HTTP 200 status code.

Response Requirements ​

HTTP Status CodeResult
200Success — no further retries
Non-200Failure — the platform will retry (see Retry Mechanism)

WARNING

The platform does not read or parse the response body. Success is determined solely by the HTTP status code. If signature verification fails, return 401 or 403.

All game copyrights, trademarks, and service marks belong to their respective owners.