1688 Product Detail API

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

API selector

1688 Sourcing

API overview

Retrieve public 1688 product, SKU, pricing, logistics, and supplier details while preserving long offer identifiers as exact strings.

Try this API

Endpoint

https://api.nexscope.ai/api/skill-api/v1/skills/1688-product-detail/run

MCP method

nexscope_1688_product_detail

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/1688-product-detail/run

Run an API

Send a JSON request body using the parameters described below.

Slug	`1688-product-detail`
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/1688-product-detail/run \
  -H "Authorization: Bearer nk-xxxxxxxxxxxxxxxxx" \
  -H "Content-Type: application/json" \
  -d '{   "offerId": "1040473674152" }'

All categories/ 1688 Sourcing

POSThttps://api.nexscope.ai/api/skill-api/v1/skills/1688-product-detail/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/1688-product-detail/run`
Auth	`Bearer API key`
Content-Type	`application/json`

Request body

Name	Type	Required	Description
`offerId`	`string`	required	Positive integer 1688 product ID. Use a string to preserve large identifiers. Example: 1040473674152
`currency`	`string`	optional	Optional three-letter currency code. The service normalizes it to uppercase. Example: USD

Request example

{
  "offerId": "1040473674152"
}

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 — requires product

Name	Type	Required	Description
`data`	`object`	required	Data value used by this API operation.
`data.product`	`object`	required	Product value used by this API operation.
`data.product.offerId`	`string`	required	Offer id value used by this API operation.
`data.product.subject`	`string`	optional	Subject value used by this API operation.
`data.product.description`	`string`	optional	Description value used by this API operation.
`data.product.productUrl`	`string`	optional	Product url value used by this API operation.
`data.product.skuList`	`array`	optional	Sku list value used by this API operation.
`data.product.saleInfo`	`object`	optional	Sale info value used by this API operation.
`data.product.shippingInfo`	`object`	optional	Shipping info value used by this API operation.
`data.product.companyName`	`string`	optional	Company name value used by this API operation.

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": {
    "product": {
      "saleInfo": {},
      "shippingInfo": {},
      "offerId": "1040473674152",
      "subject": "Example 1688 product",
      "skuList": [],
      "companyName": "Example supplier"
    }
  },
  "code": 0,
  "msg": null,
  "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

1688 Product Billboard API

Query 1688 bestseller charts for wholesale sourcing and product research. Review request parameters, response fields, and MCP usage.

1688 Product Search API

Search 1688 wholesale products for sourcing, supplier discovery, and product selection across Alibaba’s domestic B2B marketplace.

1688 Search By Image API

Find visually similar 1688 supplier products from an image URL, including price, minimum order quantity, sales, supplier, and trade data.

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_1688_product_detail",
    "arguments": {
      "offerId": "1040473674152"
    }
  }
}

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.

Pricing pendingAPI 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/1688-product-detail/run

MCP method

nexscope_1688_product_detail

API key*

JSON payload*

cURL

curl -X POST \
  https://api.nexscope.ai/api/skill-api/v1/skills/1688-product-detail/run \
  -H "Authorization: Bearer nk-..." \
  -H "Content-Type: application/json" \
  -d '{ "offerId": "1040473674152" }'

Response

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