linkfox-shopee-store-push

Shopee Push notification mechanism

Shopee Open Platform Push module(4 APIs).Depends on linkfox-shopee-store-auth as a prerequisite in the same series; forwarded via POST /shopee/developerProxy (path requires api/v2/push/...）。

How to call

• API endpoint：POST /shopee/developerProxy(different operations are distinguished by request body; for full parameters/responses/error codes see references/api.md）
• Python script：python scripts/<脚本名>.py '<JSON 参数>' [--inline](for available scripts see the script list above)
• Cost constraint: this tool consumes compute; on failure/empty results you must not automatically switch keywords, turn pages, or repeatedly probe; if continued searching is needed, first explain to the user that it will incur additional consumption.

Output strategy (default script behavior)：

• Alwayswrite the full response to <cwd>/linkfox/<YYYY-MM-DD>/<session>/data/<skill-name>-<timestamp>.json（<cwd> being the working directory when the script is executed, which in Claude Code is the current project directory;<session> taken from the environment variable SESSION_ID, automatically aggregated by user task;writing to /tmp is prohibited, if the current directory is not writable then report an error)
• Response body ≤ 8 KB: after writing to disk, print the full JSON to stdout
• Response body > 8 KB: after writing to disk, stdout outputs only a summary (top-level fields, common counts such as total/costToken, the length of the largest list field + first 3 samples)
• Add --inline to force full printing to stdout (also written to disk)

Data reading suggestions: first look at the summary to judge whether it is sufficient; when specific fields are needed, prefer to use jqorConvertFrom-Json to extract from the saved json file as needed, avoiding bringing the entire JSON into context.

Resolve authentication and compute issues

When the following abnormal situations occur, use references/onboarding.md to guide resolution:

Abnormal situations

• API Key not configured: the environment variable is not configured with LINKFOX_AGENT_API_KEY, and is also not configured with LINKFOXAGENT_API_KEY。
• Response with 401 or 402 status code
• Response indicates insufficient compute or balance: the message contains "算力余额不足/计费不足/余额不足/quota exceeded/insufficient balance/套餐到期/需充值/请充值", or content with similar meaning.

Official reference

Push module index:v2.push.set_app_push_config

---

Prerequisites

1. Run python scripts/check_auth_dependency.py；exit code 42 → first install linkfox-shopee-store-auth。
2. OAuth / Partner public API → linkfox-shopee-store-public。

Available scripts (4 APIs)

Script	API	Method
set_app_push_config.py	set_app_push_config	POST
get_app_push_config.py	get_app_push_config	GET
get_lost_push_message.py	get_lost_push_message	GET
confirm_consumed_lost_push_message.py	confirm_consumed_lost_push_message	POST
push_api.py	Common entry point	—

API description (by API)

Input parameters and response details are placed in references/apis/, SKILL retains only the index.

API	Documentation
confirm_consumed_lost_push_message	references/apis/confirm-consumed-lost-push-message.md
get_app_push_config	references/apis/get-app-push-config.md
get_lost_push_message	references/apis/get-lost-push-message.md
set_app_push_config	references/apis/set-app-push-config.md

Module overview / Feedback see references/api.md。

Usage Scenarios

1. Configure Push callback

1. set_app_push_config.py pass full POST body(callback URL, etc.)
2. get_app_push_config.py confirm configuration

2. Push missed messages again

1. get_lost_push_message.py pull missed messages
2. confirm_consumed_lost_push_message.py confirm consumed

Not Applicable

• User-side authorization flow → linkfox-shopee-store-auth
• Public OAuth / Partner query → linkfox-shopee-store-public
• Business APIs such as orders/products → corresponding business skill

Compute consumption rules

Does not consume compute.

Feedback: see references/api.md。

---

For more high-quality, professional cross-border e-commerce skills, visit LinkFox Skills.