linkfox-temu-returns-refunds-us

Query and process Temu US 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-us-w9uk5ie8v
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: linkfox-temu-returns-refunds-us
Source: https://github.com/w9uk5ie8v/LinkFoxSkills/tree/main/linkfox-temu-returns-refunds-us
Command: npx skills add https://github.com/w9uk5ie8v/LinkFoxSkills --skill linkfox-temu-returns-refunds-us-w9uk5ie8v

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Temu US sellers and developers need to handle returns, refunds, and after-sales orders programmatically, but the Partner US Returns & Refunds APIs require manual token authorization, gateway signing, and per-endpoint parameter knowledge. This Skill wraps nine Partner after-sales endpoints behind the LinkFox gateway with ready-to-run Python scripts and full request/response documentation. ## Core Features & Use Cases - After-sales order queries: List parent and child after-sales orders, fetch parent after-sales detail with refund summaries, and retrieve return logistics tracking. - Return label workflow: Get return label preparation info, query carriers, obtain signatures, and upload return labels with pick-up scheduling. - Token management: Guided Temu accessToken authorization, local token storage, and LinkFox gateway authentication helpers. - Use Case: A seller wants to process pending refunds: list parent after-sales orders by status group, pull each order's refund summary, prepare the return label, select a carrier, and upload the label — all through scripted gateway calls. ## Quick Start Set the LINKFOXAGENT_API_KEY environment variable and ask the assistant to list pending Temu US after-sales orders using your Temu accessToken with tokenPurpose order-shipping.

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

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

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

Call bg.aftersales.parentaftersales.list.get through the LinkFox gateway with a time range or status group filter to list parent after-sales orders. Then use temu.aftersales.parentaftersales.detail.get with parentOrderSn and parentAfterSalesSn to retrieve refund summaries and child order lines.

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. Finally call temu.aftersales.upload.returnlabel with parentAfterSalesSn, parentOrderSn, label URL, carrier ID, and tracking number.

What credentials does the Temu returns API require?▼

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

Does this skill handle Temu order cancellations?▼

No, buyer and seller order cancellations are covered by the separate linkfox-temu-cancel-order-us skill. This skill only covers the Partner US Returns & Refunds menu endpoints such as after-sales lists, details, return labels, and carriers.

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

Code 1002 means invalid parameters or an invalid LinkFox token, so check LINKFOXAGENT_API_KEY and request fields. Code 1003 means the forwarding to Temu failed, so verify the Temu accessToken, tokenPurpose, IP whitelist configuration, and network connectivity.