Nexscope

Temu Intelligence GB: temu/goods Detail API

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

CostRecent 32 credits / call
Try online
POST · https://api.nexscope.ai/gb/temu/goodsDetailMCP · nexscope_data_gb_temu_goods_detail
Temu Intelligence GB

What this API does

Use Temu Intelligence GB: temu/goods Detail API through Nexscope with documented parameters, structured results and API key authentication. The request accepts goodsId, regionId. Its documented result includes goods, history, regionId, title, sourceType.

Temu Intelligence GB: temu/goods Detail API API use cases

Inspect a candidate product

To inspect a candidate product, a marketplace analyst submits goodsId and regionId to Temu Intelligence GB: temu/goods Detail API. The returned goods, history, regionId help inspect the documented attributes of the candidate product.

Compare listing details

A marketplace analyst uses Temu Intelligence GB: temu/goods Detail API with goodsId and regionId to compare listing details. The returned goods, history, regionId help compare product details with another shortlisted listing.

Prepare product evidence for a sourcing review

For this workflow, a marketplace analyst calls Temu Intelligence GB: temu/goods Detail API with goodsId and regionId to prepare product evidence for a sourcing review. The result helps record product facts before a sourcing discussion.

Temu Intelligence GB: temu/goods Detail API API FAQ

What does the Temu Intelligence GB: temu/goods Detail API API return?

Use Temu Intelligence GB: temu/goods Detail API through Nexscope with documented parameters, structured results and API key authentication. The documented output includes goods, history, regionId, title, sourceType. It corresponds to the supplied goodsId, regionId. 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/goods Detail API 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 Intelligence GB: temu/goods Detail API API from my app or an MCP client?

Send a POST request to https://api.nexscope.ai/gb/temu/goodsDetail 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_goods_detail. 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/goodsDetail
MCP method
nexscope_data_gb_temu_goods_detail

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

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/goodsDetail' \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "goodsId": "601099512345678",
  "regionId": 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

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

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/goodsDetail
AuthBearer API key
Content-Typeapplication/json

Request parameters

NameTypeRequiredDescription
goodsIdstringrequired
Temu item ID, usually from searching `items[].goodsId`
regionIdintegeroptional
Temu region ID, it is recommended to use the same value as the search

Code example

{
  "goodsId": "601099512345678",
  "regionId": 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 (7 fields)

NameTypeRequiredDescription
goodsobjectoptional
Product object, fields are the same as search `items[]`
historyarrayoptional
Last 30 days history; business field can be missing or `null`
regionIdintegeroptional
The region ID used in this request
titlestringoptional
`Temu product details`
sourceTypestringoptional
`temu`
typestringoptional
`productWorkbenches`
columnsarrayoptional
Product details rendering column

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_goods_detail",
    "arguments": {
      "goodsId": "601099512345678",
      "regionId": 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.

32 credits / callAPI usage records

Try it

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

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

Related APIs