nexscope-ai/nexscope-ecommerce-skills / ecommerce-1688-product-billboard
ecommerce-1688-product-billboard
VerifiedQuery 1688 product bestseller billboard data for sourcing discovery and wholesale product research. Trigger when the user mentions 1688 product rankings, 1688 bestseller lists, wholesale hot products, domestic sourcing rankings, dropshipping product selection, 1688 trending products, bulk purchase popular items, supplier product rankings, 1688 billboard, 1688 bestsellers, sourcing rankings, wholesale hot products, trending product rankings, supplier rankings, 1688 trends. Even if the user does not explicitly mention "1688 billboard", if their need involves discovering hot-selling wholesale products or sourcing opportunities on the 1688 platform, this skill should also be triggered.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 12.0 KB |
| manifest.json | config | 316 B |
| references/api.md | markdown | 9.2 KB |
| scripts/1688_product_billboard.py | script | 9.5 KB |
references/api.md
View on GitHub# 1688 Product Billboard API Reference
## API Specification
- **Endpoint**: `${NEXSCOPE_PROXY_BASE}/api/v1/tools/research/dld/productBillboard`
- **HTTP Method**: POST, Content-Type: application/json
- **Authentication**: Header `Authorization: Bearer <api_key>`, api_key is read from environment variable `NEXSCOPE_API_KEY` (if not configured, follow the authentication guidance in SKILL.md)
`NEXSCOPE_PROXY_BASE` defaults to `https://api.nexscope.ai`. Invoking this Skill consumes credits. HTTP 401 means Nexscope authentication failed; HTTP 402 means insufficient credits. Do not substitute another buyer/store after marketplace authorization failure or automatically retry paid requests.
## Request Parameters
POST Body (JSON):
| Parameter | Type | Required | Description |
|------|------|------|------|
| keyWord | string | No | Product search keyword (search keyword must be in Chinese; if not, translate it first), max length 50 |
| date | string | No | Query time. Weekly chart: pass the Sunday date of that week, e.g. `2025-06-15` (up to 90 days); Monthly chart: pass the first day of the month, e.g. `2025-06-01` (up to one year) |
| pageType | integer | No | Billboard type: `2` = weekly, `3` = monthly. Default `3` |
| pageIndex | integer | No | Page number (starting from 1), default `1` |
| pageSize | integer | No | Number of results per page (10-100), default `20` |
| sortField | string | No | Sort field, default `orderCount`. Options: `orderCount` (order count), `saleCount` (units sold), `saleVolume` (estimated sales amount), `offerCreateTime` (listing time), `price` (wholesale price), `consignPrice` (dropship price) |
| sortType | string | No | Sort order: `desc` (descending), `asc` (ascending), default `desc` |
| searchType | integer | No | Product keyword search type: `1` = fuzzy match, `3` = exact match. Default `1` |
| offerType | integer | No | Product tag: `0` = no limit, `2` = new product, `3` = 1688 Select, `4` = cross-border, `5` = customization supported, `6` = store highlight. Default `0` |
| companyType | integer | No | Company type: `0` = no limit, `1` = store, `2` = factory |
| shiLiType | string | No | Seller membership type (multi-select), comma-separated. Options: `superFactory` (Super Factory), `Power` (Power Seller), `TrustPass` (TrustPass member only) |
| beginTpYear | integer | No | Start TrustPass years |
| endTpYear | integer | No | End TrustPass years |
| beginPrice | number | No | Wholesale price (start) |
| endPrice | number | No | Wholesale price (end) |
| beginConsignPrice | number | No | Dropship price (start) |
| endConsignPrice | number | No | Dropship price (end) |
| beginOrderCount | integer | No | Order count (start) |
| endOrderCount | integer | No | Order count (end) |
| beginSaleCount | integer | No | Units sold (start) |
| endSaleCount | integer | No | Units sold (end) |
| beginSaleVolume | number | No | Sales amount (start) |
| endSaleVolume | number | No | Sales amount (end) |
| beginStartQuantity | integer | No | Minimum order quantity (start) |
| endStartQuantity | integer | No | Minimum order quantity (end) |
| beginOfferCreateTime | string | No | Listing time (start), format: `YYYY-MM-DD` |
| endOfferCreateTime | string | No | Listing time (end), format: `YYYY-MM-DD` |
| sendTime | string | No | Delivery time (multi-select), comma-separated. Options: `24` (24 hours), `48` (48 hours), `72` (72 hours) |
| proxyRights | string | No | Dropship rights (multi-select), comma-separated. Options: `4360897` (one-piece dropship with free shipping), `449154` (procure now, pay later) |
| shopService | string | No | Seller services (multi-select), comma-separated. Options: `4057409` (Safe Buy), `888777` (Deep Verification Report) |
| buyerProtections | string | No | Comma-separated provider-localized labels. English meanings: free shipping, 7-day free returns, shipping insurance. Translate to exact Chinese provider values before sending; these English meanings are not wire enum values. |
| faceToFaceSupport | string | No | Waybill support (multi-select), comma-separated. Options: `441218` (Taobao), `386434` (Douyin), `422914` (Pinduoduo), `422978` (Xiaohongshu), `386370` (Kuaishou) |
| productIds | string | No | Product IDs, separated by the Chinese enumeration delimiter `、` for multiple, max 20 |
| goodsUrl | string | No | Product link URL |
## 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 | Total record count |
| type | string | Render style |
| columns | array | Render columns |
| products | array | Product list (see Product Object below) |
### Product Object
| Field | Type | Description |
|------|------|------|
| offerId | string | Product ID |
| asin | string | Product number |
| title | string | Product title |
| price | number | Wholesale price |
| consignPrice | number | Dropship price |
| currency | string | Currency |
| unit | string | Unit |
| quantityBegin | integer | Minimum order quantity |
| quantityPrices | string | Price range |
| salesOrderCount | integer | Order count (returns corresponding value based on statistical period) |
| salesQuantity | integer | Units sold (returns corresponding value based on statistical period) |
| estimatedSalesAmount | integer | Estimated sales amount (returns corresponding value based on statistical period) |
| dataType | string | Data type: `weeklyData` = weekly data, `monthlyData` = monthly data |
| availableDate | string | Product listing time, format `yyyy-MM-dd HH:mm:ss` |
| deliveryTime | string | Delivery time |
| levelName | string | Category hierarchy name |
| company | string | Store name |
| shopId | string | Store ID |
| shopUrl | string | Store link URL |
| asinUrl | string | Product link URL |
| imageUrl | string | Image URL |
| sourceType | string | Source platform (1688) |
| sourceTool | string | Source tool |
## 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 authentication guidance in SKILL.md. |
| Insufficient credits | HTTP 402: follow the authentication guidance in SKILL.md. |
## curl Example
This product-ID lookup can be sent without keyword translation. For an English keyword request, the Agent first translates the keyword into Simplified Chinese, then sends the prepared payload.
```bash
curl -X POST ${NEXSCOPE_PROXY_BASE:-https://api.nexscope.ai}/api/v1/tools/research/dld/productBillboard \
-H "Authorization: Bearer ${NEXSCOPE_API_KEY}" \
-H "Content-Type: application/json" \
-d '{
"productIds": "805578065498",
"pageType": 3,
"date": "2026-03-01",
"sortField": "orderCount",
"sortType": "desc",
"pageSize": 20,
"pageIndex": 1
}'
```
---
## 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: 322k | 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: 322k | 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: 322k | Updated | Claude CodeCodex | Verified | Install |