GeekBI Temu Site List API

REST API and MCP service documentation generated from server-side API definitions. Responses use the shared code, msg, and data envelope.

API selector

Temu Marketplace Intelligence

API overview

Browse Temu site records through GeekBI and use returned identifiers in related marketplace research operations.

Try this API

Endpoint

https://api.nexscope.ai/api/skill-api/v1/skills/geekbi-temu-site-list/run

MCP method

nexscope_geekbi_temu_site_list

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 .

POSThttps://api.nexscope.ai/api/skill-api/v1/skills/geekbi-temu-site-list/run

Run an API

Send a JSON request body using the parameters described below.

Slug	`geekbi-temu-site-list`
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.

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.

Example request

curl -X POST https://api.nexscope.ai/api/skill-api/v1/skills/geekbi-temu-site-list/run \
  -H "Authorization: Bearer nk-xxxxxxxxxxxxxxxxx" \
  -H "Content-Type: application/json" \
  -d '{}'

All categories/ Temu Marketplace Intelligence

POSThttps://api.nexscope.ai/api/skill-api/v1/skills/geekbi-temu-site-list/run

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/api/skill-api/v1/skills/geekbi-temu-site-list/run`
Auth	`Bearer API key`
Content-Type	`application/json`

Request body

No required request fields are defined for this API.

Request example

{}

Response body

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`	`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.

Any of option 1

Name	Type	Required	Description
`data`	`object`	required	Data value used by this API operation.
`data.total`	`integer \| null`	optional	Number of returned records.
`data.columns`	`array \| null`	optional	Provider render column metadata.
`data.columns[]`	`any`	required	Item in data columns.
`data.title`	`string \| null`	optional	Provider render/source metadata.
`data.type`	`string \| null`	optional	Provider render/source metadata.
`data.sourceType`	`string \| null`	optional	Provider render/source metadata.
`data.sourceTool`	`string \| null`	optional	Provider render/source metadata.
`data.sites`	`array \| null`	optional	Supported Temu sites.
`data.sites[]`	`object`	required	Item in data sites.
`data.sites[].regionId`	`integer \| null`	optional	Provider identifier; searches use regionId and known category IDs.
`data.sites[].siteId`	`integer \| null`	optional	Provider identifier; searches use regionId and known category IDs.
`data.sites[].name`	`string \| null`	optional	Provider name.
`data.sites[].cnName`	`string \| null`	optional	Provider cnName.
`data.sites[].lang`	`string \| null`	optional	Provider lang.
`data.sites[].currency`	`string \| null`	optional	Provider currency.

Any of option 2

Name	Type	Required	Description
`data`	`null`	required	Data value used by this API operation.

Response example

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

{
  "data": {
    "columns": [],
    "total": 0,
    "sites": []
  },
  "code": 0,
  "msg": "ok",
  "ts": "0",
  "time": "2026-01-01 00:00:00",
  "cost": "-1",
  "traceId": null
}

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.

Related APIs

GeekBI Temu Category Research API

Use GeekBI Temu Category Research with documented parameters and structured results for ecommerce research through Nexscope.

GeekBI Temu Keyword Research API

Use GeekBI Temu Keyword Research with documented parameters and structured results for ecommerce research through Nexscope.

GeekBI Temu Product Search API

Use GeekBI Temu Product Search with documented parameters and structured results for ecommerce research through Nexscope.

GeekBI Temu Product Detail API

Use GeekBI Temu Product Detail with documented parameters and structured results for ecommerce research through Nexscope.

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/api/skill-api/v2/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.

Call a tool

{
  "jsonrpc": "2.0",
  "id": "tool-call-1",
  "method": "tools/call",
  "params": {
    "name": "nexscope_geekbi_temu_site_list",
    "arguments": {}
  }
}

Legacy MCP v1

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

GET / POST /api/skill-api/v1/mcp

Online test

Execute the current API with your API key and JSON payload.

0 Credits/callAPI usage records

Try it

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

Endpoint

https://api.nexscope.ai/api/skill-api/v1/skills/geekbi-temu-site-list/run

MCP method

nexscope_geekbi_temu_site_list

API key*

JSON payload*

cURL

curl -X POST \
  https://api.nexscope.ai/api/skill-api/v1/skills/geekbi-temu-site-list/run \
  -H "Authorization: Bearer nk-..." \
  -H "Content-Type: application/json" \
  -d '{}'

Response

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