Nexscope

GeekBI Temu Keyword Research 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

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

Try this API
Endpoint
https://api.nexscope.ai/api/skill-api/v1/skills/geekbi-temu-keyword-search/run
MCP method
nexscope_geekbi_temu_keyword_search

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-keyword-search/run

Run an API

Send a JSON request body using the parameters described below.

Sluggeekbi-temu-keyword-search
HeadersAuthorization: Bearer nk-...
Content-Type: application/json
Request bodyAPI-specific JSON object.
Response bodyPlatform envelope: code, msg, data, ts, time, cost, traceId. Inspect data.status for asynchronous completion.

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.

Example request

curl -X POST https://api.nexscope.ai/api/skill-api/v1/skills/geekbi-temu-keyword-search/run \
  -H "Authorization: Bearer nk-xxxxxxxxxxxxxxxxx" \
  -H "Content-Type: application/json" \
  -d '{   "regionId": 211,   "page": 1,   "size": 3,   "keyword": "dress" }'
All categories/ Temu Marketplace Intelligence

Related APIs

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

32 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-keyword-search/run
MCP method
nexscope_geekbi_temu_keyword_search
cURL
curl -X POST \
  https://api.nexscope.ai/api/skill-api/v1/skills/geekbi-temu-keyword-search/run \
  -H "Authorization: Bearer nk-..." \
  -H "Content-Type: application/json" \
  -d '{ "regionId": 211, "page": 1, "size": 3, "keyword": "dress" }'
Response
No response yet. Run the request to see the response here.