## Overview
Qimen is Alibaba's official gateway standard for connecting ERPs with WMS/logistics systems. All requests POST to one router URL, the method parameter selects the business API, and MD5 signing with app_key/app_secret provides authentication. Most deep Jushuitan data (Taobao-order details, outbound lines, sub-warehouse stock) is only available through Qimen custom interfaces: the request pins target_app_key to 23060081 (Jushuitan) and carries a customer_id that routes to the specific merchant.
### Common parameters
| Parameter | Meaning |
| --- | --- |
| method | API name, e.g. taobao.qimen.stock.query, jushuitan.saleout.list.query |
| app_key | Taobao open-platform AppKey |
| target_app_key | Target system AppKey — 23060081 for Jushuitan |
| customer_id | Jushuitan merchant routing id, obtained during authorization |
| timestamp | yyyy-MM-dd HH:mm:ss |
| v / format / sign_method | version 2.0, response format, md5 |
| sign | Signature |
### Signing
1. Sort all parameters except sign ascending by name (ASCII).
2. Concatenate key+value with no separators.
3. Prepend and append the app_secret.
4. MD5 and uppercase the hex — that is the sign.
### Notes
- Qimen custom interfaces carry their own rate limits (Jushuitan commonly QPS 10); sync jobs need throttling and backoff retry built in.
- customer_id ↔ merchant bindings are fixed at authorization time; multi-merchant ISVs must keep a per-merchant routing table.