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.

Cost10 credits / callOnline Test

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. Review The Documented 1688 Confirm Receive Operation

Prompt: Review the documented 1688 Confirm Receive operation using ali order ID [ALI_ORDER_ID], confirm receive [CONFIRM_RECEIVE]. Summarize only the returned evidence and keep missing values explicit.

What You Need to Provide

Provide ali order ID [ALI_ORDER_ID], confirm receive [CONFIRM_RECEIVE]. Follow the Arguments section for accepted formats, limits and conditional inputs.

When using a keyword, provide Simplified Chinese text. For charts, choose a supported weekly or monthly reporting date; a chart period is not the request time.

Missing results remain unavailable. Multiple targets or time windows can require multiple calls; do not infer trends from a single snapshot.

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

Authentication

Use OAuth 2.1 Authorization Code with PKCE and the mcp:tools scope. API keys remain supported as a compatibility option.

Authorization: Bearer nk-xxxxxxxxxxxxxxxxx

Using an API key? Get your key from API Access and include it in the Authorization header shown above.

Call this MCP tool

MCP tool name

nexscope_data_alibaba1688_confirm_receive

MCP endpoint

https://api.nexscope.ai/mcp

JSON-RPC method

tools/call

Initialize 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 HTTP

Progress 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.

Example Q&A

A verified answer example is not available for this tool. Review the documented parameters and use Online Test to obtain a result with your own inputs.

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

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

{
  "jsonrpc": "2.0",
  "id": "1688-confirm-receive-example",
  "method": "tools/call",
  "params": {
    "name": "nexscope_data_alibaba1688_confirm_receive",
    "arguments": {
      "aliOrderId": "3309156590237728779",
      "confirmReceive": false
    }
  }
}

MCP Response Format

{
  "jsonrpc": "2.0",
  "id": "1688-confirm-receive-example",
  "result": {
    "content": [
      {
        "type": "text",
        "text": "{\"code\":0,\"cost\":\"0\",\"data\":{\"aliOrderId\":\"3309156590237728779\",\"success\":true},\"msg\":null,\"time\":\"2026-10-20T00:00:00Z\",\"traceId\":null,\"ts\":\"0\"}"
      }
    ],
    "structuredContent": {
      "code": 0,
      "cost": "0",
      "data": {
        "aliOrderId": "3309156590237728779",
        "success": true
      },
      "msg": null,
      "time": "2026-10-20T00:00:00Z",
      "traceId": null,
      "ts": "0"
    },
    "isError": false
  }
}