Capability Specifications

Poizon V2 API Documentation

Base URL: https://openapi.dajisaas.com
All Poizon endpoints are under the /poizonV2/ path.

I. Overview & Access

1. Supported capabilities

Keyword search, product detail, prepaid balance query, order creation & payment, order query, order cancellation, and logistics trace query.

2. Notes

Poizon access must be activated separately. Contact the platform to enable Poizon for your Access Key before calling any /poizonV2/* endpoint.
All orders are paid with your prepaid balance. Make sure your balance is sufficient before creating an order — you can check it with the Balance Query API. If procurement fails after the order is created, the prepaid amount is refunded.
Recipient addresses must be within Mainland China.
Poizon APIs are pull-based. The platform does not push order or logistics status to your system. Please poll Query Order Info and Query Logistics Trace for updates.
Product search keywords: Chinese keywords go to dwSpuTitle, English keywords go to distSpuTitle. Search results are returned in both Chinese and English.
Signature rules are identical to the other platforms — see API Signature Rules (Sign). No change is required if you already have a working signature implementation.

II. Response Format & Error Handling

1. Standard envelope (most APIs)

{
  "code": 200,
  "message": "success",
  "data": { },
  "timestamp": 1756012800000,
  "traceId": "a1b2c3d4e5f6",
  "cost": 235
}

Field	Type	Description
code	integer	`200` means success
message	string	Result description
data	object	Business data
timestamp	integer	Server timestamp, UTC milliseconds
traceId	string	Trace ID — please include it when reporting an issue
cost	integer	Server processing time, in milliseconds

2. Simplified envelope (Keyword Search & Product Detail)

These two APIs return a simplified envelope — note the field is msg (not message) and there is no traceId:

{ "code": 200, "msg": "success", "data": { }, "status": 200 }

Each API page states which envelope it uses.

3. Error response

Failures return HTTP 400 with a problem-detail body — not the envelope above:

{
  "type": "about:blank",
  "title": "Bad Request",
  "status": 400,
  "detail": "40002:order not exist",
  "instance": "/poizonV2/order/cancelOrder"
}

Field	Description
status	HTTP status code
detail	Error detail. For parameter errors: `field:message`. For Poizon business errors: `code:message` passed through from Poizon
instance	The endpoint that was called

Recommended client logic: treat HTTP 2xx + code == 200 as success; on HTTP 400, read detail.

4. Common errors

Scenario	Example `detail`
Missing required parameter	`requestId:requestId cannot be empty`
Access Key not activated for Poizon	`site config not found`
Signature failure	`sign verify fail`
Poizon business error	`40002:order not exist`
Insufficient prepaid balance	Passed through from Poizon in `detail`

Poizon V2 API Documentation#

I. Overview & Access#

1. Supported capabilities#

2. Notes#

II. Response Format & Error Handling#

1. Standard envelope (most APIs)#

2. Simplified envelope (Keyword Search & Product Detail)#

3. Error response#

4. Common errors#