linkfox-temu-returns-refunds-global

Query and manage Temu Global returns, refunds, and after-sales orders via LinkFox gateway APIs.

17|3|Updated Jun 18, 2026
One-click install
npx skills add https://github.com/w9uk5ie8v/LinkFoxSkills --skill linkfox-temu-returns-refunds-global-w9uk5ie8v
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: linkfox-temu-returns-refunds-global
Source: https://github.com/w9uk5ie8v/LinkFoxSkills/tree/main/linkfox-temu-returns-refunds-global
Command: npx skills add https://github.com/w9uk5ie8v/LinkFoxSkills --skill linkfox-temu-returns-refunds-global-w9uk5ie8v

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Temu Global sellers and developers need to handle returns, refunds, and after-sales orders programmatically, but the Partner Global Returns & Refunds APIs require manual token authorization, gateway signing, and scattered documentation. This Skill wraps 9 Partner after-sales APIs behind the LinkFox gateway with ready-to-run Python scripts and per-endpoint reference docs. ## Core Features & Use Cases - After-sales order queries: List parent and child after-sales orders, fetch parent after-sales detail with refund summaries, and look up return logistics by parentAfterSalesSn. - Return label workflow: Get label preparation info (warehouses, pick-up windows), query carriers, obtain signatures, and upload return labels through dedicated scripts. - Token management: Guided Temu accessToken authorization, local token storage with storeKey reuse, and LinkFox gateway key validation. - Use Case: A seller pulls pending parent after-sales orders for the last 24 hours, retrieves refund details for each, then uploads return labels with carrier and tracking numbers. ## Quick Start Ask the agent to list pending Temu Global after-sales orders from the past week using your saved storeKey, then show the refund summary for a specific parentAfterSalesSn.

Frequently Asked Questions about linkfox-temu-returns-refunds-global

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I query Temu Global after-sales orders via API?▼

Call bg.aftersales.parentaftersales.list.get through the LinkFox gateway with a time range or status group filter, then use the returned parentAfterSalesSn with detail, child-list, or logistics endpoints. The included Python scripts handle gateway authentication and parameter forwarding.

How to upload a return label for a Temu after-sales order?▼

First call temu.aftersales.returnlabel.prepare.get to get warehouses and pick-up windows, then temu.aftersales.carrier.get for carrier IDs, and finally temu.aftersales.upload.returnlabel with parentOrderSn, parentAfterSalesSn, label URL, carrier, and tracking number.

What credentials does the Temu returns API require?▼

Two tokens are needed: a LinkFox user key (LINKFOXAGENT_API_KEY) sent in Authorization and Token headers, and a Temu accessToken copied manually from the seller console's authorization management page. Tokens can be saved locally and referenced by storeKey.

Does this skill handle Temu order cancellations?▼

No. Buyer or seller order cancellations are covered by the separate linkfox-temu-cancel-order-global skill. This skill only covers the Partner Global Returns & Refunds menu: after-sales lists, details, return logistics, addresses, labels, carriers, and signatures.

Why does the Temu gateway return error code 1002 or 1003?▼

Code 1002 means invalid parameters or an invalid LinkFox token, so verify LINKFOXAGENT_API_KEY and request fields. Code 1003 means the upstream forwarding failed, usually due to an expired Temu accessToken, wrong tokenPurpose, or a missing IP whitelist entry.