Temu Category Search API
REST API and MCP service documentation generated from server-side API definitions. Responses use the shared code, msg, and data envelope.
API selector
REST API and MCP service documentation generated from server-side API definitions. Responses use the shared code, msg, and data envelope.
Find synced Temu category names and IDs by keyword for use in product and store filtering. View request parameters, response fields, and MCP usage.
https://api.nexscope.ai/api/skill-api/v1/skills/temu-category-search/runnexscope_temu_category_searchAll run endpoints require a user API key. Send it as a bearer token in the Authorization header.
Authorization: Bearer nk-xxxxxxxxxxxxxxxxxhttps://api.nexscope.ai/api/skill-api/v1/skills/temu-category-search/runRequest parameters documented by ecommerce.temu-category-search.
| Slug | temu-category-search |
| Headers | Authorization: Bearer nk-...Content-Type: application/json |
| Request body | API-specific JSON object. |
| Response body | Platform envelope: code, msg, data, ts, time, cost, traceId. Inspect data.status for asynchronous completion. |
| 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. |
Replace YOUR_API_KEY, then run this command in your terminal.
curl -X POST 'https://api.nexscope.ai/api/skill-api/v1/skills/temu-category-search/run' \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"pageSize": 50,
"keyword": "home",
"page": 1
}'https://api.nexscope.ai/api/skill-api/v1/skills/temu-category-search/runSend a JSON request to execute this API and receive the documented response payload.
| Method | POST |
| Path | https://api.nexscope.ai/api/skill-api/v1/skills/temu-category-search/run |
| Auth | Bearer API key |
| Content-Type | application/json |
| Name | Type | Required | Description |
|---|---|---|---|
keyword | string | required | Keyword, at most 200 characters; matches category Chinese name, English name, or category ID substring. Example: home |
page | integer | optional | Page number, at least 1; defaults to 1. Example: 1 |
pageSize |
{
"pageSize": 50,
"keyword": "home",
"page": 1
}Platform response envelope. code 0 indicates success or acceptance; data contains the business result.
{
"data": {
"total": 1,
"categories": [
{
"id": "example-id",
"categoryId": "example-id",
"parentId": "example-id",
"level": 1,
"isDeleted": 1,
"hasChildren": false
}
]
},
"code": 0,
"msg": null,
"ts": "0",
"time": "2026-01-01 00:00:00",
"cost": "-1",
"traceId": null
}| Name | Type | Required | Description |
|---|---|---|---|
data | any | required | Data value used by this API operation. |
code | integer | required | 0 means accepted or successful; nonzero is a platform error. |
msg | string | null | required | Msg value used by this API operation. |
ts |
| 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. |
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.
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/api/skill-api/v2/mcp
MCP-Protocol-Version: 2025-11-25
Content-Type: application/jsonOAuth clients request the mcp:tools scope. The endpoint's 401 response advertises protected-resource metadata for authorization discovery.
{
"jsonrpc": "2.0",
"id": "tool-call-1",
"method": "tools/call",
"params": {
"name": "nexscope_temu_category_search",
"arguments": {
"pageSize": 50,
"keyword": "home",
"page": 1
}
}
}Existing API-key clients can continue using the compatibility endpoint. New integrations should use MCP v2.
GET / POST /api/skill-api/v1/mcpExecute the current API with your API key and JSON payload.
Send a real request with the same contract shown in the reference.
https://api.nexscope.ai/api/skill-api/v1/skills/temu-category-search/runnexscope_temu_category_searchcurl -X POST \
https://api.nexscope.ai/api/skill-api/v1/skills/temu-category-search/run \
-H "Authorization: Bearer nk-..." \
-H "Content-Type: application/json" \
-d '{ "pageSize": 50, "keyword": "home", "page": 1 }'No response yet. Run the request to see the response here.
Browse Temu site records through GeekBI and use returned identifiers in related marketplace research operations.
Use GeekBI Temu Category Research with documented parameters and structured results for ecommerce research through Nexscope.
Use GeekBI Temu Keyword Research with documented parameters and structured results for ecommerce research through Nexscope.
Use GeekBI Temu Product Search with documented parameters and structured results for ecommerce research through Nexscope.
integer |
| optional |
Results per page, from 1 to 200; defaults to 50. Example: 50 |
string |
| required |
Epoch milliseconds. |
time | string | required | Server local time: yyyy-MM-dd HH:mm:ss. |
cost | string | required | Elapsed milliseconds, never credits; -1 outside web requests. |
traceId | string | null | required | Trace id value used by this API operation. |
| Name | Type | Required | Description |
|---|---|---|---|
data | object | required | Data value used by this API operation. |
data.total | integer | optional | Number of results returned on this page Example: 1 |
data.categories | array | optional | List of matching categories Example: [] |
data.categories[] | object | required | Item in data categories. |
data.categories[].id | string | optional | Category ID Example: example-id |
data.categories[].categoryId | string | optional | Category ID (upstream category id) Example: example-id |
data.categories[].parentId | string | optional | Parent category ID (empty string for top-level) Example: example-id |
data.categories[].level | integer | optional | Category hierarchy level Example: 1 |
data.categories[].categoryName | string | optional | Category name (Chinese) Example: null |
data.categories[].categoryNameEn | string | optional | Category name (English) Example: null |
data.categories[].isDeleted | integer | optional | Whether deleted: 0=Normal, 1=Deleted Example: 1 |
data.categories[].hasChildren | boolean | optional | Whether has child categories Example: false |
data.title | string | optional | Provider title for the Temu category search; the documented upstream value is in Chinese. Example: null |
data.type | string | optional | Provider-specific render or payload type. Example: null |
data.sourceType | string | optional | Provider-specific source platform type. Example: null |
data.sourceTool | string | optional | Provider-specific source tool name. Example: null |
data.costToken | integer | optional | Token cost reported by the upstream provider. Example: null |
data.costTime | integer | optional | Execution time reported by the upstream provider. Example: null |
data.page | integer | optional | Current page returned by the upstream provider. Example: null |
data.pageSize | integer | optional | Page size returned by the upstream provider. Example: null |
data.pageItemCount | integer | optional | Item count on the current page returned by the upstream provider. Example: null |
data.totalPage | integer | optional | Total page count returned by the upstream provider. Example: null |
data.dataSnapshotMonth | string | optional | Data snapshot month returned by the upstream provider. Example: null |
| Name | Type | Required | Description |
|---|---|---|---|
data | null | required | Data value used by this API operation. |