Shopee Open Platform Logistics module(46 APIs).Depends on linkfox-shopee-store-auth store selection; via POST /shopee/developerProxy pass in shopId(or merchantId), the server parses the token and forwards (path must be api/v2/logistics/...）。
How to call
- API endpoint：
POST /shopee/developerProxy(different operations are distinguished via the request body; for complete parameters/responses/error codes seereferences/api.md） - Python script：
python scripts/logistics_api.py '<JSON 参数>' [--inline](available scripts are listed in the script overview above) - Cost constraint: This tool consumes compute; on failure/empty results, do not automatically switch keywords, paginate, or repeatedly probe; if you need to continue searching, first explain to the user that additional consumption will be incurred.
Output strategy (default script behavior)：
- Alwayswrite the complete response to
<cwd>/linkfox/<YYYY-MM-DD>/<session>/data/linkfox-shopee-store-logistics-<timestamp>.json（<cwd>is the working directory when the script runs, which in Claude Code is the current project directory;<session>is taken from the environment variableSESSION_ID, automatically aggregated according to the user's task;writing to /tmp is prohibited, if the current directory is not writable, report an error) - Response body ≤ 8 KB: after writing to disk, print the complete 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 + the first 3 samples) - Add
--inlineto force full printing to stdout (also written to disk)
Data reading suggestions: First look at the summary to determine whether it is sufficient; when specific fields are needed, prefer using jqorConvertFrom-Json to extract on demand from the saved json file, avoiding bringing the entire JSON into the 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
LINKFOX_AGENT_API_KEY, andLINKFOXAGENT_API_KEY。 - Response 401 or 402 status code
- Response indicates insufficient compute or balance: The message contains "insufficient compute balance/insufficient billing/insufficient balance/quota exceeded/insufficient balance/package expired/recharge required/please recharge", or content with a similar meaning.
Official reference
Logistics module index:v2.logistics.get_shipping_parameter
Prerequisites (must read first)
- Run
python scripts/check_auth_dependency.py；exit code 42 → first installlinkfox-shopee-store-authand authorize the store. - Do notimplement authorization/token logic within this skill.
Core Concepts
- Forwarding chain：
developerProxy（shopId/merchantIdstore selection, server injects token) → ZiNiaoshopee-proxy→ Shopee API - Typical shipping process：
get_shipping_parameter→ship_order→get_tracking_number→ shipping label (create_shipping_document→download_shipping_document） - Order query(list/detail) →
linkfox-shopee-store-orders; this skill handleslogistics shipping and shipping labels - Store-level API: usually pass
shopId
Available scripts (46 APIs in the Logistics module)
| Group | Script |
|---|---|
| Shipping | get_shipping_parameter.py、ship_order.py、mass_ship_order.py、batch_ship_order.py、update_shipping_order.py |
| Waybill/tracking | get_tracking_number.py、get_tracking_info.py、update_tracking_status.py |
| Shipping label | get_shipping_document_parameter.py、create_shipping_document.py、download_shipping_document.py、create_shipping_document_job.py etc. |
| Address/channel | get_address_list.py、get_channel_list.py、update_address.py、set_address_config.py |
| Booking | get_booking_shipping_parameter.py、ship_booking.py and booking label series |
| General entry | logistics_api.py(JSON contains api field) |
See the full list at references/api.md. Shared:_shopee_logistics_common.py、_logistics_endpoints.py、_logistics_api_runner.py。
API reference (by API)
Input parameters and response details are in references/apis/, the SKILL only keeps the index.
Module overview / Feedback see references/api.md。
Usage Scenarios
1. Single order shipment
- orders skill get
order_sn(status READY_TO_SHIP) get_shipping_parameter.py：order_snship_order.pypass the completebodyget_tracking_number.pyget the tracking number
2. Print label
get_shipping_document_parameter.pycreate_shipping_document.pydownload_shipping_document.py
Calling principles
- First look at
developerProxy.httpStatus, then read the*Responsefield - GET: business parameters go at the top level of the JSON (runner assembles the queryString)
- POST: complex interfaces pass
body - Each script docstring contains the official documentation URL（
module=95）
Not Applicable
- Store authorization →
linkfox-shopee-store-auth - Order query/cancel/split →
linkfox-shopee-store-orders - Return and refund →
linkfox-shopee-store-returns - Store information →
linkfox-shopee-store-shop - Product listing →
linkfox-shopee-store-product - FirstMile first-leg →
linkfox-shopee-store-first-mile - SBS warehouse inventory →
linkfox-shopee-store-sbs - FBS Brazil warehouse →
linkfox-shopee-store-fbs
Compute consumption rules
No compute is consumed.
Feedback:
Auto-detect and report feedback via the Feedback API when any of the following apply:
- The functionality or purpose described in this skill does not match actual behavior
- The skill's results do not match the user's intent
- The user expresses dissatisfaction or praise about this skill
- Anything you believe could be improved
Call the feedback API as specified in references/api.md. Do not interrupt the user's flow.
For more high-quality, professional cross-border e-commerce skills, visit LinkFox Skills.