1688 Procurement
1688 Order Detail MCP
Read one 1688 buyer order by its exact string ID, including product, amount and logistics fields when available. Requires the current buyer's authorization.
1688 Order Detail AI Prompts & Use Cases
After connecting this MCP tool to your AI assistant, you can ask the questions below. Replace bracketed placeholders with your own inputs and use the supported values in Arguments.
New to Nexscope MCP? Follow the connection guide, then use the prompts below. The Integration and Parameters & Response tabs contain the connection steps, call example, and technical reference.
1. Inspect A Buyer Order
Prompt: Show the details for my 1688 order [ORDER_ID]. Keep the order ID as a string and report its returned status and product lines.
2. Review Order Amounts
Prompt: For my 1688 order [ORDER_ID], show the available amount fields with their documented units. Keep missing amounts unknown rather than treating them as zero.
3. Check Available Shipping Details
Prompt: For my 1688 order [ORDER_ID], show the shipping information returned with the order. If logistics fields are absent, say that they are unavailable.
What You Need to Provide
Provide an exact 1688 order ID as a string. Use only the current buyer's authorization; optional logistics data may be absent.
Step 1 · Connect
Connect Your AI Assistant
Connect a compatible MCP client to Nexscope, then select this tool from your assistant. Use the connection settings in your client to complete authentication.
POST https://api.nexscope.ai/mcp
MCP-Protocol-Version: 2025-11-25
Content-Type: application/jsonAuthentication
Use OAuth 2.1 Authorization Code with PKCE and the mcp:tools scope. API keys remain supported as a compatibility option.
Authorization: Bearer nk-xxxxxxxxxxxxxxxxxUsing an API key? Get your key from API Access and include it in the Authorization header shown above.
Call this MCP tool
nexscope_data_alibaba1688_order_detailhttps://api.nexscope.ai/mcptools/callInitialize an MCP 2025-11-25 Streamable HTTP session at https://api.nexscope.ai/mcp, then use tools/call.
{
"jsonrpc": "2.0",
"id": "1688-order-detail-1",
"method": "tools/call",
"params": {
"name": "nexscope_data_alibaba1688_order_detail",
"arguments": {
"aliOrderId": "9007199254740993"
}
}
}MCP 2025-11-25 · Streamable HTTPProgress is delivered on the original POST SSE response. GET SSE carries notifications; reconnecting must query existing asynchronous work rather than submit again.
Arguments
| Name | Type | Required | Description |
|---|---|---|---|
aliOrderId | string | required | Positive 1688 order ID as a JSON string. Example: 9007199254740993 |
Response fields
Treat structuredContent as the programmatic API response payload.
| Name | Type | Required | Description |
|---|---|---|---|
aliOrderId | string | required | Positive 1688 order ID; send as a JSON string to preserve precision. Pattern: ^[1-9][0-9]{0,18}$ |
aliStatus | string | required | Ali status value used by this API operation. |
baseInfo | object | required | Base info value used by this API operation. |
nativeLogistics | object | optional | Native logistics value used by this API operation. |
normalizedStatus | string | required | Normalized status value used by this API operation. |
productItems | array | optional | Product items value used by this API operation. |
productItems[] | object | required | Item in productItems. |
Workflow Guide
Workflow example, not a verified API response.
Your Goal
What can I check with an exact 1688 order ID?
Suggested Steps
Workflow example: submit the exact order ID as a string under the current buyer's 1688 authorization. Review the returned status, product lines, amounts, and any available logistics fields. Optional fields may be absent. No verified buyer order response is published for this page.
About this sample: Workflow guidance only; no private order or live response is included.
Published sample data is not available for this page. A format illustration or workflow guide is not a substitute for a published result.
View the MCP Request & Response Format
Examples
Workflow example, not a verified API response.
The JSON-RPC envelope below illustrates how the shown arguments and payload fit into MCP. It is not captured network traffic or proof of a successful call. Workflow-only examples do not include a result.
MCP Request
No verified MCP request example is available. Refer to Integration and the documented requirements before preparing a call.
MCP Response Format
This workflow does not claim an API result. No verified response example is available; refer to Parameters & Response for the documented response structure.