Nexscope

Temu Intelligence GB: temu/site List API

Use Temu Intelligence GB: temu/site List API through Nexscope with documented parameters, structured results and API key authentication.

CostRecent 10 credits / call
Try online
POST · https://api.nexscope.ai/gb/temu/siteListMCP · nexscope_data_gb_temu_site_list
Temu Intelligence GB

What this API does

Use Temu Intelligence GB: temu/site List API through Nexscope with documented parameters, structured results and API key authentication. Its documented result includes errcode, errmsg, sites, siteId, regionId, name, cnName, lang.

Temu Intelligence GB: temu/site List API API use cases

Investigate Temu Intelligence GB: temu/site List API

To investigate temu intelligence gb: temu/site list api, a marketplace analyst submits the operation-specific inputs to Temu Intelligence GB: temu/site List API. The returned errcode, errmsg, sites help investigate the requested operation.

Collect Temu Intelligence GB: temu/site List API evidence

A marketplace analyst uses Temu Intelligence GB: temu/site List API with the operation-specific inputs to collect temu intelligence gb: temu/site list api evidence. The returned errcode, errmsg, sites help compare evidence for the requested scope.

Review Temu Intelligence GB: temu/site List API results

For this workflow, a marketplace analyst calls Temu Intelligence GB: temu/site List API with the operation-specific inputs to review temu intelligence gb: temu/site list api results. The result helps review the returned facts with the team.

Temu Intelligence GB: temu/site List API API FAQ

What does the Temu Intelligence GB: temu/site List API API return?

Use Temu Intelligence GB: temu/site List API through Nexscope with documented parameters, structured results and API key authentication. The documented output includes errcode, errmsg, sites, siteId, regionId, name, cnName, lang. 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 Intelligence GB: temu/site List API API cost?

The current documented cost is Recent 10 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 Intelligence GB: temu/site List API API from my app or an MCP client?

Send a POST request to https://api.nexscope.ai/gb/temu/siteList 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_gb_temu_site_list. The same documented request parameters apply; use Online test to review a request before adding it to your app.

View plans and creditsConnect this API with MCP

Try this API
Endpoint
https://api.nexscope.ai/gb/temu/siteList
MCP method
nexscope_data_gb_temu_site_list

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/siteList

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/siteList' \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{}'

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

CodeDescription
200HTTP request completed. Check JSON code; only 0 indicates business success or acceptance.
400Request JSON or required API parameters are invalid.
401API key is missing, invalid, or cannot be matched to a user.
5xxAPI execution or upstream service failed.
All categories/ Temu Intelligence GB
POSThttps://api.nexscope.ai/gb/temu/siteList

Run this API

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

Endpoint

MethodPOST
Pathhttps://api.nexscope.ai/gb/temu/siteList
AuthBearer API key
Content-Typeapplication/json

Request parameters

No required request fields are defined for this API.

Code example

{}

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 (12 fields)

NameTypeRequiredDescription
errcodeintegeroptional
Business status; success is `200`
errmsgstringoptional
Status text; `ok` on success
sitesarrayoptional
Supported Temu sites
totalintegeroptional
Number of sites
columnsarrayoptional
Render column definition
siteIdinteger / stringoptional
Upstream internal ID, not used for product, category, keyword or store filtering
regionIdintegeroptional
Temu region ID accepted by other endpoints; should be a non-empty positive integer
namestringoptional
Site name
cnNamestringoptional
Site Chinese name
langstringoptional
site language
currencystringoptional
site currency
extraFieldsobjectoptional
Upstream extension field, may be missing

Responses

CodeDescription
200HTTP request completed. Check JSON code; only 0 indicates business success or acceptance.
400Request JSON or required API parameters are invalid.
401API key is missing, invalid, or cannot be matched to a user.
5xxAPI 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_gb_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 /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.

10 credits / callAPI usage records

Try it

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

Endpoint
/gb/temu/siteList
MCP method
nexscope_data_gb_temu_site_list
cURL
curl -X POST \
  https://api.nexscope.ai/gb/temu/siteList \
  -H "Authorization: Bearer nk-..." \
  -H "Content-Type: application/json" \
  -d '{}'
Response
No response yet. Run the request to see the response here.

Related APIs