linkfox-temu-returns-refunds-global
Original:🇺🇸 English
Translated
24 scriptsChecked / no sensitive code detected
Temu 全球站电商退货与退款 API,经 LinkFox 网关转发 Partner Global Returns & Refunds / 售后退货退款 相关 bg/temu 接口(退货申请、退款、售后单查询与处理等,接口将按 Partner 文档逐条接入)。当用户提到 Temu Global 退货、退款、售后退货、return、refund、aftersales return、parentAfterSalesSn、退货单、退款单、order-shipping 售后 时触发。买家/卖家取消订单用 linkfox-temu-cancel-order-global / linkfox-temu-cancel-order-global;订单用 linkfox-temu-order-global。
6installs
Added on
NPX Install
npx skill4agent add linkfox-ai/linkfox-skills linkfox-temu-returns-refunds-globalTags
Translated version includes tags in frontmatterSKILL.md Content
View Translation Comparison →Temu 全球站 — 退货与退款(Returns & Refunds)
本 skill()覆盖 Partner Platform for Global Returns & Refunds / 电商退货与退款(及关联 After-sales 退货退款类)相关 / 接口( 与各 以 Partner 后台为准,见 partner-global-catalog.md)。
linkfox-temu-returns-refunds-globalbg.*temu.*menu_codesub_menu_code已接入 9 条 Partner Return and Refund 接口,清单见 partner-global-catalog.md。
网关(本 skill 内置):
| 能力 | 方法 | 路径 |
|---|---|---|
退货退款 OpenAPI( | POST | |
| 加签文件下载 | POST | |
相关 skill
| 场景 | skill |
|---|---|
| 退货与退款(本 skill) | |
| 买家发起取消订单(非退货退款全流程) | |
| 卖家发起取消订单 / 缺货取消 / 申诉 | |
| 订单列表/详情/金额/售后上下文 | |
| 商品管理 | |
| 履约/发货 | |
| 网关与 Temu token | 本 skill |
API Usage
| 文档 | 内容 |
|---|---|
| api.md | 网关、鉴权、错误码、接入约定 |
| partner-global-catalog.md | 接口目录 + Partner URL + 脚本(随接入更新) |
| apis/README.md | 按接口分文件( |
默认参数
| 字段 | 默认 | 说明 |
|---|---|---|
| site | | Partner Global |
| managementType | | 半托管(具体接口以 Partner 文档为准) |
| tokenPurpose | | 订单/售后场景 token(见 access-token.md) |
鉴权
- LinkFox:→ Header
LINKFOXAGENT_API_KEY+AuthorizationToken - Temu:或
accessToken(storeKey时建议带storeKey)tokenPurpose=order-shipping
Scripts
| 脚本 | 说明 |
|---|---|
| 任意 |
| 加签文件下载 |
| |
| |
| |
| |
| |
| |
| |
| |
| |
接入更多接口(约定)
你每提供一条 Partner 文档( + + URL + Request/Response 参数表),将:
typesub_menu_code- 新增 (完整入参/出参层级)
references/apis/<type-slug>.md - 新增 (调用
scripts/global_returns_refunds_<slug>.py)_global_returns_refunds_script.run_cli - 更新 partner-global-catalog.md、apis/README.md 与本表
示例(通用代理)
bash
export LINKFOXAGENT_API_KEY="<key>"
python scripts/temu_global_proxy.py '{
"accessToken": "TOKEN",
"tokenPurpose": "order-shipping",
"type": "<TEMU_API_TYPE>",
"params": {
"request": {}
}
}'Feedback: :
skillNamelinkfox-temu-returns-refunds-global网关与授权脚本
| 脚本 | 说明 |
|---|---|
| 校验 LinkFox 用户 Token |
| Temu accessToken 后台授权步骤 |
| 保存 accessToken 到本地 |
| 列出已保存 token |
| 读取已保存 token |
| 通用网关转发(多 site) |
| 加签文件下载(多 site) |
授权说明:references/access-token.md
<!-- LF_LARGE_RESPONSE_BLOCK -->
Handling Large Responses
To avoid overflowing the agent context, persist the response to disk and extract only the fields you need:
python scripts/response_io.py run --script scripts/check_linkfox_token.py --out-dir <DIR> '<params>'
python scripts/response_io.py read <file> --fields "<paths>" # or --path "<JMESPath>"Pickoutside any git working tree (e.g.--out-diron Unix,/tmp/...on Windows). Persisted responses may contain PII, pricing, or auth-sensitive data — do not commit them. Files are not auto-deleted; clean up when the task is done.%TEMP%/...
This skill exposes multiple entry scripts:,check_linkfox_token.py,get_temu_access_token.py,global_returns_refunds_aftersales_aftersales_list_get.py,global_returns_refunds_aftersales_carrier_get.py,global_returns_refunds_aftersales_parentaftersales_detail_get.py,global_returns_refunds_aftersales_parentaftersales_list_get.py,global_returns_refunds_aftersales_parentreturnorder_get.py,global_returns_refunds_aftersales_returnaddress_get.py,global_returns_refunds_aftersales_returnlabel_prepare_get.py,global_returns_refunds_aftersales_signature_get.py,global_returns_refunds_aftersales_upload_returnlabel.py,list_temu_access_tokens.py,save_temu_access_token.py,temu_file_download.py,temu_global_file_download.py,temu_global_proxy.py,temu_proxy.py. Passtemu_token_guide.pyto choose the one you need.--script scripts/<name>.py
runread--limit/--offset--format json|jsonl|csv|tableWhen to prefer this pattern — apply your judgment based on the response characteristics, e.g.:
- High field count per record, or fields you don't need
- Batch/paginated results (multiple items per call)
- Long-text fields (descriptions, reviews, HTML, time series)
- Output reused across later steps rather than consumed immediately
For small, single-use responses, calling the main script directly is fine.
⚠️ The preview is a truncated schema + sample, not the full data. Any field-level decision must read from the persisted file via .
<!-- /LF_LARGE_RESPONSE_BLOCK -->read