linkfox-temu-cancel-order-us

Executes Temu US buyer and seller order-cancellation API calls through the LinkFox gateway.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Temu US sellers and operations teams need to handle buyer-initiated cancellations and seller-side cancellations (appeals, out-of-stock) through Partner US APIs, which require correct gateway routing, dual authentication, and precise request payloads. This Skill wraps those six cancel-order endpoints behind ready-to-run scripts via the LinkFox gateway. ## Core Features & Use Cases - Buyer cancellation handling: Query pending cancel after-sales requests with bg.aftersales.cancel.list.get (filter by afterSalesStatusGroup) and approve them with bg.aftersales.cancel.agree. - Seller cancellation workflows: Submit cancel appeals (temu.order.cancel.appeal.apply), poll appeal results, file out-of-stock cancellations, and query their asynchronous review status. - Credential and token management: Validate the LinkFox API key, store Temu accessTokens locally by storeKey/site/tokenPurpose, and get guided authorization steps for each shop type. - Use Case: A seller sees a buyer cancellation request on a US order; the agent lists pending cancellations with afterSalesStatusGroup=8, retrieves the parentAfterSalesSn and parentOrderSn, then calls the agree endpoint to approve the cancellation. ## Quick Start Ask the agent to list pending Temu US buyer cancellation requests and approve one using your saved storeKey with tokenPurpose order-shipping.

Frequently Asked Questions about linkfox-temu-cancel-order-us

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

FAQPage Schema
How do I approve a buyer cancellation request on Temu US?▼

First call bg.aftersales.cancel.list.get with afterSalesStatusGroup=8 to list pending cancellations and obtain the parentAfterSalesSn and parentOrderSn. Then call bg.aftersales.cancel.agree with those two identifiers to approve the cancellation.

How do I submit an out-of-stock cancellation for a Temu US order?▼

Call temu.order.cancel.outofstock.apply with the parentOrderSn and the orderSnList of child orders. The request goes to risk-control review, so poll temu.order.cancel.outofstock.result.get with the same identifiers to check the asynchronous applyStatus.

What credentials are required to call Temu cancel order APIs?▼

Two tokens are needed: a LinkFox user token (LINKFOXAGENT_API_KEY or a token field in the JSON) for gateway authentication, and a Temu accessToken for the store. The Temu token can be passed directly or loaded from local storage via storeKey with site, managementType, and tokenPurpose.

Which tokenPurpose should I use for Temu US order cancellation?▼

Use tokenPurpose=order-shipping with site=us and managementType=semi-managed, which are the skill defaults. This token is obtained by authorizing the Cyber-ERP app in the Temu seller console under the US Seller Central site.

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

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

Does this skill support Temu Europe or global site cancellations?▼

No, this skill only covers the US site. Use linkfox-temu-cancel-order-eu for the Europe site and linkfox-temu-cancel-order-global for other global regions, as each site has its own gateway routing and token configuration.