Skip to content

nexscope-ai/nexscope-ecommerce-skills / ecommerce-tiktok-seller-detail

ecommerce.tiktok-seller-detail

Verified

Query TikTok Shop store (seller) details, retrieving a complete store profile by sellerId with total sales, multi-period (1d/7d/30d/90d) sales and GMV, followers, rating, review count, positive feedback rate, delivery rate, response rate, in-store product count, promoting creator count, promotional video count, livestream count, price range, product categories, and estimated listing time. Trigger when users mention TikTok store detail, TikTok seller detail, TikTok store analysis, TikTok store data, TikTok store profile, TikTok Shop store detail, TikTok seller detail, Nexscope store profile. Even if the user does not explicitly mention "Nexscope" or "TikTok", trigger this skill whenever their need involves querying the full detail/profile of a specific TikTok Shop store (with a known sellerId).

FileKindSize
SKILL.mdskill md9.9 KB
manifest.jsonconfig341 B
references/api.mdmarkdown7.7 KB
scripts/tiktok_seller_detail.pyscript6.5 KB

references/api.md

View on GitHub
# Nexscope TikTok Seller Detail API Reference

## API Specification

- **Endpoint**: `${NEXSCOPE_PROXY_BASE}/api/v1/tools/research/echotik/sellerDetail`
- **HTTP Method**: POST, Content-Type: application/json
- **Authentication**: Header `Authorization: <api_key>`, api_key is read preferentially from environment variable `NEXSCOPE_API_KEY`, falling back to `NEXSCOPE_API_KEY` (if not configured, follow the **## Resolving Authentication and Credit Issues** section in SKILL.md)
- **User-Agent**: `Nexscope-Skill/2.0`
- **Timeout**: 120s

## Request Parameters

POST Body (JSON):

  | Parameter | Type | Required | Default | Description |  
|------|------|------|--------|------|
| sellerId | string | Yes | - | TikTok Shop seller ID. Obtainable from the "Nexscope TikTok Seller Search" skill (`nexscope-echotik-list-seller`) results, or from the ID in a known store link. Max length 1000 |

## 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

On success, the business object inside the platform `data` field is flat: seller details are direct properties of that object, alongside `columns` and `type`. **This endpoint has no business `total` or `sellers` list.**

### Status and Render Fields

| Field | Type | Description |
|------|------|------|
| costToken | integer | Token cost |
| columns | array | Render column definitions (display metadata) |
| type | string | Render style (e.g., `tableListWorkbenches`) |

### Seller Detail Fields

| Field | Type | Description |
|------|------|------|
| sellerId | string | Store ID |
| sellerName | string | Store name |
| sellerLink | string | Store link |
| coverUrl | string | Store cover image URL |
| region | string | Region |
| categoryId | string | Primary category ID |
| categoryL2Id | string | Secondary category ID |
| categoryL3Id | string | Tertiary category ID |
| totalSaleCnt | integer | Total sales |
| totalSale1dCnt | integer | Sales in last 1 day (increment) |
| totalSale7dCnt | integer | Sales in last 7 days (increment) |
| totalSale30dCnt | integer | Sales in last 30 days (increment) |
| totalSale90dCnt | integer | Sales in last 90 days (increment) |
| totalSaleGmvAmt | number | Total GMV |
| totalSaleGmv1dAmt | number | GMV in last 1 day (increment) |
| totalSaleGmv7dAmt | number | GMV in last 7 days (increment) |
| totalSaleGmv30dAmt | number | GMV in last 30 days (increment) |
| totalSaleGmv90dAmt | number | GMV in last 90 days (increment) |
| followersCount | integer | Follower count |
| rating | number | Rating |
| reviewCount | integer | Review count |
| positiveFeedbackRate | number | Positive feedback rate |
| responseRate | number | Response rate |
| deliveryRate | integer | Delivery rate |
| totalProductCnt | integer | Historical product count in store (including delisted) |
| totalCrawlProductCnt | integer | Current product count in store |
| spuAvgPrice | number | Average SKU price across the store |
| minPrice | integer | Minimum price |
| maxPrice | integer | Maximum price |
| totalIflCnt | integer | Total promoting creator count |
| totalVideoCnt | integer | Total promotional video count |
| totalLiveCnt | integer | Total livestream count |
| salesFlagText | string | Primary selling method (video sales / livestream sales) |
| salesTrendFlagText | string | Sales trend (rising / falling / stable) |
| shopIdentityLabel | string | Store identity (e.g., OFFICIAL SHOP) |
| shopTypeText | string | Whether a brand store (Yes / No) |
| fromFlagText | string | Cross-border identifier (local / cross-border) |
| productCategoryList | string | Product categories (JSON string, containing category_name / category_id) |
| mostProductCategoryList | string | TOP1 product category (JSON string) |
| firstCrawlDt | integer | Estimated listing time, in yyyyMMdd format (e.g., 20240504 represents 2024-05-04) |
| userId | string | Creator UID |
| sourceType | string | Product source (e.g., Tiktok) |
| sourceTool | string | Source tool (e.g., Nexscope-Seller Detail) |

## 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 |
|---|---|
| Parameter validation error | Parameter value is invalid (e.g., `sellerId` is empty or does not exist). Refer to `msg` for the specific reason |
| 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

### Query a single seller detail

```bash
curl -X POST ${NEXSCOPE_PROXY_BASE}/api/v1/tools/research/echotik/sellerDetail \
  -H "Authorization: Bearer ${NEXSCOPE_API_KEY}" \
  -H "Content-Type: application/json" \
  -H "User-Agent: Nexscope-Skill/2.0" \
  -d '{
    "sellerId": "7495514739648989419"
  }'
```

### Combined usage with seller search

First use seller search to list sellers in a region, take their `sellerId`, then call this endpoint:

```bash
# First obtain a sellerId with the seller search skill. Then query that seller:
curl -X POST ${NEXSCOPE_PROXY_BASE}/api/v1/tools/research/echotik/sellerDetail \
  -H "Authorization: Bearer ${NEXSCOPE_API_KEY}" \
  -H "Content-Type: application/json" \
  -H "User-Agent: Nexscope-Skill/2.0" \
  -d '{ "sellerId": "<sellerId returned from the previous step>" }'
```

---

## 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.
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: 472kUpdated Claude CodeCodexVerifiedInstall
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: 323kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 323kUpdated Claude CodeCodexVerifiedInstall
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 availableStars: 323kUpdated Claude CodeCodexVerifiedInstall