Temu Category Research

Find Temu categories to narrow your product research. Call the Temu Category Research API via REST or MCP with your Nexscope API key.

CostRecent 32 credits / call

Try online

POST · https://api.nexscope.ai/gb/temu/categorySearchMCP · nexscope_geekbi_temu_category_search

What this API does

Find Temu categories to narrow your product research. The request accepts regionId, page, size, order, sort. Its documented result includes errcode, errmsg, regionId, parentCatId.

Temu Category Research API use cases

Shortlist a market segment

To shortlist a market segment, a marketplace analyst submits regionId and page to Temu Category Research. The returned errcode, errmsg, regionId help identify categories or products worth further market research.

Compare ranked products or categories

A marketplace analyst uses Temu Category Research with regionId and page to compare ranked products or categories. The returned errcode, errmsg, regionId help compare candidates within the requested ranking scope.

Investigate candidates before sourcing

For this workflow, a marketplace analyst calls Temu Category Research with regionId and page to investigate candidates before sourcing. The result helps choose products to investigate before contacting suppliers.

Temu Category Research API FAQ

What does the Temu Category Research API return?

Find Temu categories to narrow your product research. The documented output includes errcode, errmsg, regionId, parentCatId. It corresponds to the supplied regionId, page, size, order, sort. 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 Category Research API cost?

The current documented cost is Recent 32 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 Category Research API from my app or an MCP client?

Send a POST request to https://api.nexscope.ai/gb/temu/categorySearch 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_geekbi_temu_category_search. Use the MCP arguments shown in the MCP guide, or switch Online test to MCP to review its request before adding it to your app.

View plans and credits Connect this API with MCP

Try this API

Endpoint

https://api.nexscope.ai/gb/temu/categorySearch

MCP method

nexscope_geekbi_temu_category_search

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/gb/temu/categorySearch

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/gb/temu/categorySearch' \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "keyword": "pets",
  "order": "desc",
  "page": 1,
  "regionId": 211,
  "size": 20,
  "sort": "totalSold",
  "totalSoldMin": 1000
}'

Code example

{
  "keyword": "pets",
  "order": "desc",
  "page": 1,
  "regionId": 211,
  "size": 20,
  "sort": "totalSold",
  "totalSoldMin": 1000
}

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	Default HTTP response for both success and many business errors. Only outer JSON code 0 indicates success or asynchronous acceptance; inspect data for the result.
429	Execution admission rate limit; honor Retry-After when present.
503	Execution admission is temporarily unavailable; honor Retry-After when present.
Opt-in	X-Nexscope-Http-Status: semantic maps controller-handled business errors to HTTP status on run and task routes. Pre-authentication failures, such as a missing API key (code 11209), may still return HTTP 200 before this mapping. Always check the outer JSON code; malformed requests and infrastructure failures may also return non-200 HTTP responses.

View parameters & response Try online

All categories/ Temu Intelligence GB

POSThttps://api.nexscope.ai/gb/temu/categorySearch

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/gb/temu/categorySearch`
Auth	`Bearer API key`
Content-Type	`application/json`

Request parameters

Name	Type	Required	Description
`regionId`	`integer`	optional	Temu region ID, taken from site list `sites[].regionId`
`page`	`integer`	optional	Page number
`size`	`integer`	optional	Quantity per page; `page * size` must not exceed 10000
`order`	`string`	optional	Sorting direction; no default value for gateways
`sort`	`string`	optional	Sorting fields; only use fields that the interface has confirmed to support
`keyword`	`string`	optional	Category Chinese name or English name, fuzzy search

Response example

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

No response example is published for this API. Refer to the response fields below.

Response fields

Response field reference (7 fields)

Name	Type	Required	Description
`errcode`	`integer`	optional	Business status; success is `200`
`errmsg`	`string`	optional	Status text; `ok` on success
`total`	`integer`	optional	Number of hits; possibly capped at 10,000
`regionId`	`integer`	optional	Actual query area
`columns`	`array`	optional	Render column definitions, not business results
`items`	`array`	optional	Category results; business fields may be missing or `null`
`parentCatId`	`integer`	optional	When omitted, the top category is returned; when the known `catId` is passed, the direct child level is returned

Responses

Code	Description
200	Default HTTP response for both success and many business errors. Only outer JSON code 0 indicates success or asynchronous acceptance; inspect data for the result.
429	Execution admission rate limit; honor Retry-After when present.
503	Execution admission is temporarily unavailable; honor Retry-After when present.
Opt-in	X-Nexscope-Http-Status: semantic maps controller-handled business errors to HTTP status on run and task routes. Pre-authentication failures, such as a missing API key (code 11209), may still return HTTP 200 before this mapping. Always check the outer JSON code; malformed requests and infrastructure failures may also return non-200 HTTP responses.

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_geekbi_temu_category_search",
    "arguments": {
      "keyword": "pets",
      "page": 1,
      "regionId": 211,
      "size": 3
    }
  }
}

Legacy MCP v1

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

GET / POST /mcp/legacy

What can you do with this API?

Data explained and practical use cases

AI Guide

Question

What data can Temu Category Research provide, and how might I use it?

AI answer

Search Temu category results by region and keyword, with optional numeric filters for measures such as sold items, item count, mall count, average price, and sales. The supplied response documents an items array but does not define the business fields inside each item; its example returns no items. Treat those measures as search filters, not guaranteed returned metrics.

Data category	Documented fields	What the values mean
Category results	`items`	Matching category records; their individual business fields may be absent or `null` and are not specified here.
Match count	`total`	Number of hits, possibly capped at 10,000.
Region scope	`regionId`	The actual Temu region used for the query.
Hierarchy context	`parentCatId`	Documented parent context: omitting it returns top categories; supplying a known category ID returns direct children. It is not listed among the supplied request fields.

Search for a term such as “pets” in a selected Temu region and inspect the returned category records.
- Prompt example: “I am researching products on Temu. Could you search for a term such as “pets” in a selected Temu region and inspect the returned category records? Show matching records and source links where the API provides them; ask me for any required identifier or filter.”
Narrow category research using a minimum or maximum itemCount or totalSold filter.
- Prompt example: “I am researching products on Temu. Could you narrow category research using a minimum or maximum itemCount or totalSold filter? Show matching records and source links where the API provides them; ask me for any required identifier or filter.”
Compare result counts for the same keyword across supported region IDs.
- Prompt example: “I am researching products on Temu. Could you compare result counts for the same keyword across supported region IDs? Show the returned values behind the comparison, and mark missing data.”
Page through matching categories while accounting for the documented 10,000-result limit.
- Prompt example: “I am researching products on Temu. Could you page through matching categories while accounting for the documented 10,000-result limit? Show the relevant returned evidence and tell me what input you need from me.”

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.

Recent 32 credits / callAPI usage records

Try it

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

Endpoint

/gb/temu/categorySearch

MCP method

nexscope_geekbi_temu_category_search

API key*

JSON payload*

cURL

curl -X POST \
  https://api.nexscope.ai/gb/temu/categorySearch \
  -H "Authorization: Bearer nk-..." \
  -H "Content-Type: application/json" \
  -d '{ "keyword": "pets", "order": "desc", "page": 1, "regionId": 211, "size": 20, "sort": "totalSold", "totalSoldMin": 1000 }'

Response

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

Related APIs

Temu Category List

Browse Temu categories for product research. Results come back as structured JSON.

Temu Product Detail

Look up details for a Temu product. Results come back as structured JSON.

Temu Image Search

Find Temu products similar to an image. Results come back as structured JSON.

Temu Product Search

Search Temu products for competitor and assortment research.