1688 Procurement
1688 Confirm Receive MCP
Confirm receipt of a delivered 1688 order after checking the goods. Requires an active 1688 authorization and your Nexscope API key.
1688 Confirm Receive 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. Confirm Receipt After Checking Goods
Prompt: For delivered 1688 order [ALI_ORDER_ID], wait for my explicit confirmation that I checked the goods. Then send confirmReceive=true and report the returned success value.
What You Need to Provide
Replace bracketed values with your own identifiers and inputs. Use only your own ACTIVE, unexpired 1688 store authorization.
Read the returned business status and message. An HTTP or envelope success does not prove that an order or write operation succeeded.
Obtain separate, explicit user confirmation before setting the documented confirm flag to JSON true. Never retry a write automatically.
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_confirm_receivehttps://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-confirm-receive-1",
"method": "tools/call",
"params": {
"name": "nexscope_data_alibaba1688_confirm_receive",
"arguments": {
"aliOrderId": "3309156590237728779",
"confirmReceive": false
}
}
}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 | Exact positive integer identifier. Send as a JSON string. Example: 3309156590237728779 |
confirmReceive | boolean | required | Must be JSON true after separate explicit user confirmation. Examples default to false and do not authorize this action. Example: false |
Response fields
Treat structuredContent as the programmatic API response payload.
| Name | Type | Required | Description |
|---|---|---|---|
code | integer | optional | Nexscope transport/business envelope code; 0 means the request was processed. Inspect data for operation outcomes. |
cost | string | optional | Processing time in milliseconds, not credits. |
data | object | optional | Data value used by this API operation. |
data.aliOrderId | string | optional | Exact positive integer identifier. Send as a JSON string. Pattern: ^[1-9][0-9]*$ |
data.success | boolean | optional | Success value used by this API operation. |
msg | string | null | optional | Safe response message. |
time | string | optional | Server response time. |
traceId | string | null | optional | Request trace identifier. |
ts | string | optional | Server timestamp. |
Workflow Guide
Workflow example, not a verified API response.
Your Goal
For delivered 1688 order [ALI_ORDER_ID], wait for my explicit confirmation that I checked the goods. Then send confirmReceive=true and report the returned success value.
Suggested Steps
After the goods have been checked and the user explicitly confirms receipt, send confirmReceive=true for the exact aliOrderId and inspect the returned success value.
About this sample: This is a workflow guide, not a verified API response. The example does not execute the write or confirm its outcome.
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.