nexscope-ai/nexscope-ecommerce-skills / ecommerce-tiktok-top-selling-products
ecommerce.tiktok-top-selling-products
VerifiedQuery TikTok global e-commerce market top-selling product rankings via FastMoss data, supporting daily/weekly/monthly dimensions and category-level analysis. Trigger when users mention TikTok bestseller chart, TikTok hot product ranking, TikTok sales ranking, TikTok GMV ranking, TikTok category bestsellers, TikTok weekly product report, TikTok top-selling rankings, TikTok bestseller charts, TikTok GMV ranking, TikTok category hot sellers, TikTok weekly product report, FastMoss. Even if the user does not explicitly mention "FastMoss", trigger this skill whenever their need involves viewing TikTok platform bestseller rankings or sales rankings by time dimension.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 10.3 KB |
| manifest.json | config | 329 B |
| references/api.md | markdown | 6.6 KB |
| scripts/tiktok_top_selling_products.py | script | 6.6 KB |
references/api.md
View on GitHub# FastMoss TikTok Top Selling Products API Reference
## API Specification
- **Endpoint**: `${NEXSCOPE_PROXY_BASE}/api/v1/tools/research/fastmoss/productRankTopSelling`
- **HTTP Method**: POST, Content-Type: application/json
- **Authentication**: Header `Authorization: <api_key>`, api_key is read from environment variable `NEXSCOPE_API_KEY` or `NEXSCOPE_API_KEY` (if not configured, follow the **## Resolving Authentication and Credit Issues** section in SKILL.md)
## Request Parameters
POST Body (JSON):
| Parameter | Type | Required | Description |
|------|------|------|------|
| region | string | Yes | Market region code. Options: US (United States), GB (United Kingdom), MX (Mexico), ES (Spain), DE (Germany), IT (Italy), FR (France), ID (Indonesia), VN (Vietnam), MY (Malaysia), TH (Thailand), PH (Philippines), BR (Brazil), JP (Japan), SG (Singapore) |
| dateInfo | object | Yes | Date specification object, containing `type` and `value` fields |
| dateInfo.type | string | Yes | Time granularity: `day`, `week`, `month` |
| dateInfo.value | string | Yes | Date value: day format `YYYY-MM-DD`, week format `YYYY-weekNumber` (e.g., `2025-18`), month format `YYYY-MM` |
| category | string | No | Product category name (English), matched to TikTok category ID. Non-English input must be translated to English first |
| orderby | object | No | Sort rule object, containing `field` and `order` fields |
| orderby.field | string | No | Sort field: `units_sold` (sales), `gmv` (GMV), `total_units_sold` (total sales), `total_gmv` (total GMV), `growth_rate` (growth rate) |
| orderby.order | string | No | Sort direction: `desc` (descending), `asc` (ascending), default `desc` |
| page | integer | No | Page number, default `1` |
| pageSize | integer | No | Items per page, max `10`, default `10` |
## Nexscope response envelope
These research endpoints return a platform object with numeric `code`, nullable `msg`, and business `data`. Only outer `code: 0` means success; `200`, string codes, missing codes, and HTTP 200 alone do not. A nonzero code is a platform error: show `msg` and do not interpret the payload as a successful result.
`msg` preserves the upstream message when available; Chinese messages are translated to English by Nexscope. A successful response without a message has `msg: null`. Do not infer success or retry behavior from the message text. On both success and failure, the direct fields `code`, `errcode`, `errorCode`, `msg`, `errmsg`, `message`, and `errorMsg` are removed from public `data`. Read the message only from outer `msg`; deeper business fields are preserved, including nested `code` and `status`.
Business field tables and abbreviated business examples below describe `data`, unless explicitly labeled as a complete platform response. For example, a business `products` field is at HTTP `data.products`, and a business `data` array is at HTTP `data.data`. The research endpoints already had this outer envelope; no additional wrapper is added.
```json
{"code":0,"msg":null,"data":{}}
```
Metadata includes string `ts` (epoch milliseconds), string `cost` (elapsed milliseconds, not credits), `time`, and nullable `traceId`. Handle network/HTTP failures before the platform code; gateway failures may not be platform JSON. Keep the existing billing-header guidance separate from elapsed time.
## Response Structure
| Field | Type | Description |
|------|------|------|
| total | integer | Record count |
| products | array | Hot selling product list (see product object below) |
| columns | array | Rendered columns |
| type | string | Render style |
| costToken | integer | Token cost |
### Product Object
| Field | Type | Description |
|------|------|------|
| title | string | Product name |
| productId | string | Product ID |
| region | string | Region code |
| price | number | Product price |
| minPrice | number | Minimum price |
| maxPrice | number | Maximum price |
| currency | string | Currency |
| totalSaleCnt | integer | Total sales |
| totalSale1dCnt | integer | Sales in last 1 day (returned when dateType=day) |
| totalSale7dCnt | integer | Sales in last 7 days (returned when dateType=week) |
| totalSale30dCnt | integer | Sales in last 30 days (returned when dateType=month) |
| totalSaleGmvAmt | number | Total GMV |
| totalSaleGmv1dAmt | number | GMV in last 1 day (returned when dateType=day) |
| totalSaleGmv7dAmt | number | GMV in last 7 days (returned when dateType=week) |
| totalSaleGmv30dAmt | number | GMV in last 30 days (returned when dateType=month) |
| growthRate | number | Growth rate (percentage) |
| shopName | string | Store name |
| shopTotalUnitsSold | integer | Store total sales |
| shopSellerId | string | Store seller ID |
| categoryName | string | Product category |
| productCommissionRate | number | Product commission rate (basis points, 1000=10%) |
| imageUrl | string | Product image URL |
| offShelvesText | string | Whether delisted ("Yes"=delisted, "No"=on sale) |
## Error Codes
HTTP 200 does not prove business success. Read only the numeric outer platform `code`: `0` succeeds and any other value fails. Show outer `msg`; never test removed provider codes or nested business `code` as the platform status. Authentication, permissions, balance, and validation failures may be platform errors even with HTTP 200; also handle non-2xx HTTP and non-JSON responses.
### Recovery guidance
| Condition | Action |
|---|---|
| Authentication failed | HTTP 401 or authorized error: Follow the **## Resolving Authentication and Credit Issues** section in SKILL.md. |
| Insufficient credits | HTTP 402: Follow the **## Resolving Authentication and Credit Issues** section in SKILL.md. |
## curl Example
```bash
curl -X POST ${NEXSCOPE_PROXY_BASE}/api/v1/tools/research/fastmoss/productRankTopSelling \
-H "Authorization: Bearer ${NEXSCOPE_API_KEY}" \
-H "Content-Type: application/json" \
-d '{"region": "US", "dateInfo": {"type": "day", "value": "2026-04-15"}, "page": 1, "pageSize": 10}'
```
---
## API Key request rate and retries
All API Keys of one Nexscope user share the public API execution request-rate allowance, measured in any rolling 1-second window. The allowed RPS depends on that user's entitlements; it is not a universal 1 RPS. One Skill operation may issue multiple public API requests, each of which uses the allowance.
HTTP 429 with Nexscope outer code `13012` means request-rate exhaustion: honor the response's `Retry-After`. Outer code `13013` means concurrent-request exhaustion, not rate exhaustion; honor `Retry-After` when supplied. Check the HTTP status and outer JSON code separately. Do not automatically replay writes or requests with uncertain outcomes; first reconcile the operation's state.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |