linkfox-temu-order-eu

Temu Europe Order Management API (Manage Order)

This skill (linkfox-temu-order-eu) covers Partner Platform for EU Order menu (menu_code=dbd3d395963a408984b8ae7dbc5f64f9) under 10 order bg.order.* / temu.order.* / temu.local.order.* interfaces (type aligned with US, default site=eu). For the US site, use linkfox-temu-order-us; for the global site (non-US/EU), use linkfox-temu-order-global。

See partner-eu-catalog.md。

Currently integrated 10 interfaces; the remaining order interfaces will be added one by one according to the Partner documentation to references/apis/ and eu_order_*.py。

Gateway (built into this skill)：

Capability	Method	Path
Order OpenAPI (`eu_order_*`、`temu_eu_proxy`）	POST	`https://tool-gateway.linkfox.com/temu/proxy`
signed file download	POST	`https://tool-gateway.linkfox.com/temu/fileDownload`

Related skills

Scenario	skill
Product list/details/edit/inventory/listing and delisting	`linkfox-temu-manage-product-eu`
Product publishing, categories, V2 add	`linkfox-temu-add-product-us`
Price/supply price, pricing sheet	`linkfox-temu-price-eu`
Cancel order	`linkfox-temu-cancel-order-eu`
Returns and refunds	`linkfox-temu-returns-refunds-eu`
Fulfillment/shipping (label purchase, partner warehouse, self-shipping, tracking)	`linkfox-temu-fulfillment-eu`
Gateway and Temu token	This skill `scripts/`

How to call

API endpoint：POST /temu/proxy(different operations are distinguished by the request body; for complete parameters/responses/error codes see references/api.md）
Python script：python scripts/<脚本名>.py '<JSON 参数>' [--inline](for available scripts see the script list above)
Cost constraint: This tool consumes compute; on failure/empty results, do not automatically switch keywords, paginate, or repeatedly probe; if you need to continue searching, first explain to the user that additional consumption will be incurred.

Output strategy (default script behavior)：

Alwayswrite the complete response to <cwd>/linkfox/<YYYY-MM-DD>/<session>/data/<skill-name>-<timestamp>.json（<cwd> is the working directory when the script is executed, which in Claude Code is the current project directory;<session> is taken from the environment variable SESSION_ID, automatically aggregated according to the user's task;writing to /tmp is prohibited, if the current directory is not writable, report an error)
Response body ≤ 8 KB: after writing to disk, print the complete JSON to stdout
Response body > 8 KB: after writing to disk, stdout outputs only a summary (top-level fields, common counts such as total/costToken, length of the largest list field + first 3 samples)
Add --inline to force full printing to stdout (also written to disk)

Data reading suggestions: first look at the summary to judge whether it is sufficient; when specific fields are needed, prefer using jqorConvertFrom-Json to extract on demand from the saved json file, avoiding bringing the entire JSON into context.

Documentation	Content
api.md	Gateway, authentication, error codes, extended processes
partner-eu-catalog.md	Interface directory + Partner URL + scripts (updated as integrations are added)
apis/README.md	Split into files by interface（`apis/<type-slug>.md`）

Resolve authentication and compute issues

When the following abnormal situations occur, use references/onboarding.md to guide problem resolution:

Abnormal situation

API Key not configured: the environment variable is not configured LINKFOX_AGENT_API_KEYis also not configured LINKFOXAGENT_API_KEY。
Respond with 401 or 402 status code
Respond indicating insufficient compute power or balance: The message contains "insufficient compute power balance/insufficient billing/insufficient balance/quota exceeded/insufficient balance/package expired/recharge required/please recharge", or content with a similar meaning.

Default parameters

Field	Default	Description
site	`eu`	Partner EU
managementType	`semi-managed`	Semi-managed
tokenPurpose	`order-shipping`	Order/shipping scenario token (see access-token.md）

Authentication

LinkFox：LINKFOXAGENT_API_KEY → Header Authorization + Token
Temu：accessToken or storeKey（storeKey , it is recommended to include tokenPurpose=order-shipping）

Scripts (by type)

Script	type	Status
`eu_order_list_v2_get.py`	`bg.order.list.v2.get`	Integrated
`eu_order_detail_v2_get.py`	`bg.order.detail.v2.get`	Integrated
`eu_order_shippinginfo_v2_get.py`	`bg.order.shippinginfo.v2.get`	Integrated
`eu_order_decryptshippinginfo_get.py`	`bg.order.decryptshippinginfo.get`	Integrated
`eu_order_amount_query.py`	`bg.order.amount.query`	Integrated
`eu_order_amount_v2_query.py`	`temu.order.amount.v2.query`	Integrated
`eu_order_amount_v3_query.py`	`temu.order.amount.v3.query`	Integrated
`eu_order_combinedshipment_list_get.py`	`bg.order.combinedshipment.list.get`	Integrated
`eu_order_customization_get.py`	`bg.order.customization.get`	Integrated
`eu_order_verification_upload.py`	`temu.local.order.verification.upload`	Integrated
`temu_eu_proxy.py`	Any `type`	General
`temu_eu_file_download.py`	Signed file download	General

Integrating a new API (convention)

Each time you provide a Partner document (type + parameter table + optional sub_menu_code), the following will be done:

Add references/apis/<type-slug>.md(complete input/output parameter hierarchy)
Add scripts/eu_order_<slug>.py(call _eu_order_script.run_cli）
Update partner-eu-catalog.md、apis/README.md and this table

Example

export LINKFOXAGENT_API_KEY="<key>"

# 订单列表 V2（待发货 parentOrderStatus=2）
python scripts/eu_order_list_v2_get.py '{
  "accessToken": "TOKEN",
  "tokenPurpose": "order-shipping",
  "request": {
    "pageNumber": 1,
    "pageSize": 20,
    "parentOrderStatus": 2
  }
}'

# 按父订单号查询（最多 20 个）
python scripts/eu_order_list_v2_get.py '{
  "accessToken": "TOKEN",
  "request": {
    "parentOrderSnList": ["PO-123456789"]
  }
}'

# 订单详情 V2（须 parentOrderSn）
python scripts/eu_order_detail_v2_get.py '{
  "accessToken": "TOKEN",
  "tokenPurpose": "order-shipping",
  "request": {
    "parentOrderSn": "PO-123456789"
  }
}'

# 收货地址 V2（传 parentOrderSn）
python scripts/eu_order_shippinginfo_v2_get.py '{
  "accessToken": "TOKEN",
  "tokenPurpose": "order-shipping",
  "request": {
    "parentOrderSn": "PO-123456789"
  }
}'

# 敏感收货地址解密（传 parentOrderSn）
python scripts/eu_order_decryptshippinginfo_get.py '{
  "accessToken": "TOKEN",
  "tokenPurpose": "order-shipping",
  "request": {
    "parentOrderSn": "PO-123456789"
  }
}'

# 订单金额/供货价（ERP 对账，传 parentOrderSn）
python scripts/eu_order_amount_query.py '{
  "accessToken": "TOKEN",
  "tokenPurpose": "order-shipping",
  "request": {
    "parentOrderSn": "PO-123456789"
  }
}'

# 可合并发货订单组（request 可为空对象）
python scripts/eu_order_combinedshipment_list_get.py '{
  "accessToken": "TOKEN",
  "tokenPurpose": "order-shipping",
  "request": {}
}'

# 定制商品内容（子订单号 orderSn，单次最多 10 个）
python scripts/eu_order_customization_get.py '{
  "accessToken": "TOKEN",
  "tokenPurpose": "order-shipping",
  "request": {
    "orderSnList": ["SO-123456789", "SO-987654321"]
  }
}'

# 上传 SN/IMEI 或二手鉴真（orderList[].orderSn）
python scripts/eu_order_verification_upload.py '{
  "accessToken": "TOKEN",
  "tokenPurpose": "order-shipping",
  "request": {
    "orderList": [
      {
        "orderSn": "SO-123456789",
        "verificationInfo": [
          {
            "serialNumber": "SN-001234567890",
            "imeiNumberList": ["352099001761481"]
          }
        ]
      }
    ]
  }
}'

Feedback： skillName：linkfox-temu-order-eu

Gateway and authorization scripts

Script	Description
`check_linkfox_token.py`	Verify LinkFox user Token
`temu_token_guide.py`	Temu accessToken backend authorization steps
`save_temu_access_token.py`	Save accessToken locally
`list_temu_access_tokens.py`	List saved tokens
`get_temu_access_token.py`	Read saved token
`temu_proxy.py`	General gateway forwarding (multi-site)
`temu_file_download.py`	Signed file download (multi-site)

Authorization instructions:references/access-token.md

Compute power consumption rules

Does not consume compute power.