Temu Product Research: temu/store Query API

Use Temu Product Research: temu/store Query API through Nexscope with documented parameters, structured results and API key authentication.

CostRecent Avg. 31 · Range 10–72 credits / call

Try online

POST · https://api.nexscope.ai/eh/temu/storeQueryMCP · nexscope_data_eh_temu_store_query

Temu Product Research

What this API does

Use Temu Product Research: temu/store Query API through Nexscope with documented parameters, structured results and API key authentication. The request accepts searchKey, siteId, category, isLocal, orderTotalMin. Its documented result includes storeNum, stores, title, sourceType, storeId, siteId, storeName, logoUrl.

Temu Product Research: temu/store Query API API use cases

Investigate a seller or store

To investigate a seller or store, a marketplace analyst submits searchKey and siteId to Temu Product Research: temu/store Query API. The returned storeNum, stores, title help identify the store associated with a candidate product.

Compare storefront product evidence

A marketplace analyst uses Temu Product Research: temu/store Query API with searchKey and siteId to compare storefront product evidence. The returned storeNum, stores, title help compare products or listings across shortlisted storefronts.

Shortlist stores for further research

For this workflow, a marketplace analyst calls Temu Product Research: temu/store Query API with searchKey and siteId to shortlist stores for further research. The result helps choose stores for a supplier or competitor review.

Temu Product Research: temu/store Query API API FAQ

What does the Temu Product Research: temu/store Query API API return?

Use Temu Product Research: temu/store Query API through Nexscope with documented parameters, structured results and API key authentication. The documented output includes storeNum, stores, title, sourceType, storeId, siteId, storeName, logoUrl. It corresponds to the supplied searchKey, siteId, category, isLocal, orderTotalMin. Optional fields can be absent; a missing value should not be interpreted as a measured zero. Example values illustrate the response shape, rather than live account results.

How many credits does the Temu Product Research: temu/store Query API API cost?

The current documented cost is Recent Avg. 31 · Range 10–72 credits / call. This is the same cost shown at the top of this page. If a range or estimate is displayed, the final charge depends on the request. Review your available credits and the pricing page before calling the API, and check API usage records for the actual charge.

How do I call the Temu Product Research: temu/store Query API API from my app or an MCP client?

Send a POST request to https://api.nexscope.ai/eh/temu/storeQuery with your API key as a Bearer token and the JSON inputs shown in API integration. In a compatible MCP client such as Claude or Cursor, connect Nexscope and call nexscope_data_eh_temu_store_query. The same documented request parameters apply; use Online test to review a request before adding it to your app.

View plans and credits Connect this API with MCP

Try this API

Endpoint

https://api.nexscope.ai/eh/temu/storeQuery

MCP method

nexscope_data_eh_temu_store_query

Step 1 of 3 · Authenticate

Authentication

All run endpoints require a user API key. Send it as a bearer token in the Authorization header.

Authorization: Bearer nk-xxxxxxxxxxxxxxxxx

Missing or invalid API keys return an authentication error. Manage keys from .

Step 2 of 3 · Send a request

POSThttps://api.nexscope.ai/eh/temu/storeQuery

Run an API

Send a JSON request body using the parameters described below.

Example request

Replace YOUR_API_KEY, then run this command in your terminal.

curl -X POST 'https://api.nexscope.ai/eh/temu/storeQuery' \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "page": 1,
  "pageSize": 20,
  "searchKey": "home",
  "siteId": "211"
}'

Step 3 of 3 · Inspect the result

Check the response

Read code for the request status and data for the result. Open the parameter and response reference for the full field definitions.

HTTP status codes

Code	Description
200	HTTP request completed. Check JSON code; only 0 indicates business success or acceptance.
400	Request JSON or required API parameters are invalid.
401	API key is missing, invalid, or cannot be matched to a user.
5xx	API execution or upstream service failed.

View parameters & response Try online

All categories/ Temu Product Research

POSThttps://api.nexscope.ai/eh/temu/storeQuery

Run this API

Send a JSON request to execute this API and receive the documented response payload.

Open tester

Endpoint

Method	`POST`
Path	`https://api.nexscope.ai/eh/temu/storeQuery`
Auth	`Bearer API key`
Content-Type	`application/json`

Request parameters

Name	Type	Required	Description
`searchKey`	`string`	optional	Store name or ID keyword
`siteId`	`string`	optional	Country site ID, multiple commas separated (e.g. 211=United States, 76=United Kingdom)
`category`	`string`	optional	Backend category ID, multiple commas separated
`isLocal`	`string`	optional	Whether it is semi-managed or not: 0=fully managed, 1=semi-managed
`orderTotalMin`	`integer`	optional	Total sales range (starting)
`orderTotalMax`	`integer`	optional	Total sales range (end)
`orderWeekMin`	`integer`	optional	Weekly sales range (starting)
`orderWeekMax`	`integer`	optional	Weekly sales range (end)
`orderMonthMin`	`integer`	optional	Monthly sales range (starting)
`orderMonthMax`	`integer`	optional	Monthly sales range (end)
`totalRevenueMin`	`number`	optional	Total sales range (USD, starting)
`totalRevenueMax`	`number`	optional	Total sales range (USD, end)
`weekRevenueMin`	`number`	optional	Weekly sales range (USD, starting)
`weekRevenueMax`	`number`	optional	Weekly sales range (USD, end)
`monthRevenueMin`	`number`	optional	Monthly sales range (USD, starting)
`monthRevenueMax`	`number`	optional	Monthly sales range (USD, end)
`ratingMin`	`number`	optional	Rating interval (start)
`ratingMax`	`number`	optional	Rating interval (end)
`reviewNumMin`	`integer`	optional	Comment count range (starting)
`reviewNumMax`	`integer`	optional	Comment count interval (end)
`followerNumMin`	`integer`	optional	Number of fans range (starting)
`followerNumMax`	`integer`	optional	Number of fans range (end)
`productNumMin`	`integer`	optional	Product number range (start)
`productNumMax`	`integer`	optional	Product number range (end)
`listedTimeBegin`	`string`	optional	Store opening date range (start)
`listedTimeEnd`	`string`	optional	Store opening date range (end)
`sortBy`	`string`	optional	Sorting field + direction: `order_week_count-0` (weekly sales in descending order, default), `order_count-0`, `total_revenue-0`, `rating-0` Example: order_week_count-0
`page`	`integer`	optional	Page number (starting from 1) Example: 1
`pageSize`	`integer`	optional	Number of items per page, maximum 100 Example: 20

Code example

{
  "page": 1,
  "pageSize": 20,
  "searchKey": "home",
  "siteId": "211"
}

Response example

Platform response envelope. code 0 indicates success or acceptance; data contains the business result.

{
  "code": 0,
  "cost": "-1",
  "data": {},
  "msg": null,
  "time": "2026-01-01 00:00:00",
  "traceId": null,
  "ts": "0"
}

Response fields

Response field reference (25 fields)

Name	Type	Required	Description
`total`	`integer`	optional	Number of items returned on this page
`storeNum`	`integer`	optional	Total number of eligible stores (upstream `store_num`)
`stores`	`array`	optional	Temu store list
`columns`	`array`	optional	Rendered columns
`title`	`string`	optional	Title (`Temu Store Query`)
`sourceType`	`string`	optional	Source type: temu
`type`	`string`	optional	Rendered style: tableListWorkbenches
`storeId`	`store_id`	optional	Store ID
`siteId`	`site_id`	optional	Country Site ID
`storeName`	`store_name`	optional	Store name
`logoUrl`	`logo_url`	optional	Store Logo URL
`orderTotal`	`order_total`	optional	total sales
`orderWeek`	`order_week`	optional	Weekly sales
`orderMonth`	`order_month`	optional	monthly sales
`totalRevenue`	`total_revenue`	optional	total sales
`weekRevenue`	`week_revenue`	optional	weekly sales
`monthRevenue`	`month_revenue`	optional	monthly sales
`rating`	`-`	optional	Rating
`listedTime`	`listed_time`	optional	Store opening time
`reviewNum`	`review_num`	optional	Number of comments
`followerNum`	`follower_num`	optional	Number of fans
`productNum`	`product_num`	optional	Number of items
`categoriesCn`	`categories_cn`	optional	Chinese category list
`categories`	`-`	optional	English category list
`isLocal`	`is_local`	optional	Whether it is semi-managed or not: 0=fully managed, 1=semi-managed

Responses

Code	Description
200	HTTP request completed. Check JSON code; only 0 indicates business success or acceptance.
400	Request JSON or required API parameters are invalid.
401	API key is missing, invalid, or cannot be matched to a user.
5xx	API execution or upstream service failed.

Data source, freshness, and limitations

Source, freshness, coverage, rate limits, and estimation notes are not specified in this API definition unless they appear in the request or response field documentation above. Do not assume official marketplace data or real-time freshness when it is not explicitly documented.

Step 1 of 2 · Connect your MCP client

MCP

V2 recommended

Connect remote agents through the standard MCP 2025-11-25 Streamable HTTP endpoint. Use OAuth 2.1 Authorization Code with PKCE, or an API key for compatibility.

POST https://api.nexscope.ai/mcp
MCP-Protocol-Version: 2025-11-25
Content-Type: application/json

Authentication

OAuth clients request the mcp:tools scope. The endpoint's 401 response advertises protected-resource metadata for authorization discovery.

Step 2 of 2 · Call the tool

Call a tool

{
  "jsonrpc": "2.0",
  "id": "tool-call-1",
  "method": "tools/call",
  "params": {
    "name": "nexscope_data_eh_temu_store_query",
    "arguments": {
      "page": 1,
      "pageSize": 20,
      "searchKey": "home",
      "siteId": "211"
    }
  }
}

Legacy MCP v1

Existing API-key clients can continue using the compatibility endpoint. New integrations should use MCP v2.

GET / POST /mcp/legacy

Online test

Execute the current API with your API key and JSON payload. Online tests use this site's configured API environment; the Endpoint and copyable examples use the public integration address.

50 credits / callAPI usage records

Try it

Send a real request with the same contract shown in the reference.

Endpoint

/eh/temu/storeQuery

MCP method

nexscope_data_eh_temu_store_query

API key*

JSON payload*

cURL

curl -X POST \
  https://api.nexscope.ai/eh/temu/storeQuery \
  -H "Authorization: Bearer nk-..." \
  -H "Content-Type: application/json" \
  -d '{ "page": 1, "pageSize": 20, "searchKey": "home", "siteId": "211" }'

Response

No response yet. Run the request to see the response here.

Use Temu Product Research: temu/product Query API through Nexscope with documented parameters, structured results and API key authentication.

Temu Product Research: temu/temu Category Search API

Use Temu Product Research: temu/temu Category Search API through Nexscope with documented parameters, structured results and API key authentication.

What this API does

Temu Product Research: temu/store Query API API use cases

Investigate a seller or store

Compare storefront product evidence

Shortlist stores for further research

Temu Product Research: temu/store Query API API FAQ

What does the Temu Product Research: temu/store Query API API return?

How many credits does the Temu Product Research: temu/store Query API API cost?

How do I call the Temu Product Research: temu/store Query API API from my app or an MCP client?

Authentication

Run an API

Example request

Check the response

HTTP status codes

Run this API

Endpoint

Request parameters

Code example

Response example

Response fields

Responses

Data source, freshness, and limitations

MCP

Call a tool

Legacy MCP v1

Online test

Try it

Related APIs