linkfox-temu-cancel-order-eu

Run Temu Partner EU buyer and seller order-cancellation APIs 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-eu-w9uk5ie8v
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: linkfox-temu-cancel-order-eu
Source: https://github.com/w9uk5ie8v/LinkFoxSkills/tree/main/linkfox-temu-cancel-order-eu
Command: npx skills add https://github.com/w9uk5ie8v/LinkFoxSkills --skill linkfox-temu-cancel-order-eu-w9uk5ie8v

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Temu Partner EU sellers need to handle buyer-initiated cancellation requests and submit seller-side cancellations (appeals or out-of-stock) through authenticated OpenAPI calls, which requires managing LinkFox gateway credentials, Temu access tokens, and per-interface request schemas. ## Core Features & Use Cases - Buyer cancellation handling: Query pending buyer cancellation after-sales requests with bg.aftersales.cancel.list.get and approve them with bg.aftersales.cancel.agree. - Seller cancellation workflows: Submit cancellation appeals (temu.order.cancel.appeal.apply), out-of-stock cancellations (temu.order.cancel.outofstock.apply), and poll their review results. - Credential management: Save, list, and retrieve Temu access tokens locally by storeKey, site, and tokenPurpose, with an authorization guide for each shop type. - Use Case: A seller lists pending buyer cancellations with afterSalesStatusGroup=8, agrees to them, then submits an out-of-stock cancellation for another order and polls the review status. ## Quick Start Set the LINKFOXAGENT_API_KEY environment variable and ask the agent to list pending Temu EU buyer cancellation requests using the eu_cancel_aftersales_cancel_list_get script with your Temu access token.

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

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

FAQPage Schema
How do I list and approve buyer cancellation requests on Temu EU?▼

Call bg.aftersales.cancel.list.get with afterSalesStatusGroup=8 to fetch pending buyer cancellations, then pass the returned parentAfterSalesSn and parentOrderSn to bg.aftersales.cancel.agree. Both run through the eu_cancel scripts with your accessToken and tokenPurpose order-shipping.

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

Run eu_seller_cancel_order_cancel_outofstock_apply.py with the parentOrderSn and orderSnList from your order data. The request goes to risk-control review, and you poll temu.order.cancel.outofstock.result.get with the same order identifiers for the applyStatus.

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

You need two tokens: a LinkFox user token set as LINKFOXAGENT_API_KEY for gateway authentication, and a Temu accessToken copied manually from the seller console authorization page. Alternatively, save the Temu token locally and reference it by storeKey with site eu and tokenPurpose order-shipping.

Does this skill work for Temu US or global site cancellations?▼

No, this skill targets Partner EU only with default site eu. Use linkfox-temu-cancel-order-us for the US site and linkfox-temu-cancel-order-global for other regions, as each site routes to a different Temu OpenAPI gateway.

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

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