1688 Procurement
1688 Create Order MCP
Submit a 1688 procurement order using the selected products, SKUs, and delivery details. Requires an active 1688 authorization and your Nexscope API key.
1688 Create Order 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. Submit A Confirmed Procurement Order
Prompt: Use my selected cargoParamList [CARGO_ITEMS] and delivery address [ADDRESS_ID] to prepare a 1688 order. Show the items and address for my review; only after my separate explicit confirmation send confirmCreateOrder=true. Return the actual orderId or upstream error.
2. Submit An Order With A Supplied Address
Prompt: Use my cargoParamList [CARGO_ITEMS] and supplied addressParam [ADDRESS] for a 1688 procurement order. Review the chosen delivery details and wait for my explicit confirmation before sending confirmCreateOrder=true. Report the returned code, message and orderId.
3. Create An Order With A Distribution Flow
Prompt: Prepare my 1688 order using cargoParamList [CARGO_ITEMS], addressId [ADDRESS_ID], the documented distribution flow [FLOW] and fenxiaoChannel [CHANNEL]. Show the selected settings and wait for my separate explicit confirmation before sending confirmCreateOrder=true. Report the actual orderId or error.
4. Create An Order With Cross-Border Logistics
Prompt: Prepare my 1688 order using cargoParamList [CARGO_ITEMS], addressId [ADDRESS_ID] and the documented isvBizType [BUSINESS_TYPE] and selected crossBorderLogisticsSolutionId [SOLUTION_ID] with useBorderLogisticsSolution=true. Review the logistics selection with me, then wait for separate explicit confirmation before sending confirmCreateOrder=true. Report the actual order result.
5. Select A Documented Trade Type
Prompt: Prepare my 1688 order using cargoParamList [CARGO_ITEMS], addressId [ADDRESS_ID] and the documented tradeType [TRADE_TYPE]. Explain the selected trade type without assuming payment succeeded. After my separate explicit confirmation, send confirmCreateOrder=true and report the returned orderId or error.
6. Use A Documented Promotion
Prompt: Prepare my 1688 order with cargoParamList [CARGO_ITEMS], addressId [ADDRESS_ID], shopPromotionId [PROMOTION_ID] and useRedEnvelope [Y_OR_N]. Show the settings without promising a discount. After my separate explicit confirmation, send confirmCreateOrder=true and report the actual order result.
7. Include A Client Order Reference And Message
Prompt: Prepare my 1688 order with cargoParamList [CARGO_ITEMS], addressId [ADDRESS_ID], outOrderId [CLIENT_ORDER_ID] and message [ORDER_MESSAGE]. Preserve my supplied values; do not infer idempotency from outOrderId. After my separate explicit confirmation, send confirmCreateOrder=true and report the returned orderId.
8. Set The Documented Anonymous Buyer Option
Prompt: Prepare my 1688 order with cargoParamList [CARGO_ITEMS], addressId [ADDRESS_ID] and the documented anonymousBuyer option [ANONYMOUS_BUYER]. Show the selected value without promising privacy effects beyond the documented field. After my separate explicit confirmation, send confirmCreateOrder=true and report the actual order result.
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_create_orderhttps://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-create-order-1",
"method": "tools/call",
"params": {
"name": "nexscope_data_alibaba1688_create_order",
"arguments": {
"addressId": "987654321012345678",
"cargoParamList": [
{
"offerId": "1234567890123456789",
"quantity": 2,
"specId": "example-spec"
}
],
"confirmCreateOrder": false,
"flow": "general"
}
}
}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 |
|---|---|---|---|
addressId | string | optional | Select from receiveAddressList. |
addressParam | object | optional | addressParam |
addressParam.address | string | required | Street address. |
addressParam.areaText | string | optional | Area text value used by this API operation. |
addressParam.cityText | string | optional | City text value used by this API operation. |
addressParam.fullName | string | required | Recipient name. |
addressParam.mobile | string | required | Recipient phone; avoid sharing outside the request. |
addressParam.phone | string | optional | Landline phone number. |
addressParam.postCode | string | optional | Postal code. |
addressParam.provinceText | string | optional | Province text value used by this API operation. |
anonymousBuyer | boolean | optional | Anonymous buyer value used by this API operation. |
cargoParamList | array | required | cargoParamList Minimum items: 1 |
cargoParamList[] | object | required | cargoParamList |
cargoParamList[].offerId | string | required | Exact positive integer identifier. Send as a JSON string. Pattern: ^[1-9][0-9]*$ |
cargoParamList[].quantity | integer | required | Quantity in the selling unit. Minimum: 1 |
cargoParamList[].specId | string | optional | SKU specification identifier. |
confirmCreateOrder | boolean | required | Must be JSON true after separate explicit user confirmation. Examples default to false and do not authorize this action. Default: false |
crossBorderLogisticsSolutionId | string | optional | Cross-border logistics solution sourceId. |
fenxiaoChannel | string | optional | Distribution platform. Allowed: douyin, kuajing, pinduoduo, taote |
flow | string | optional | Order flow; defaults to general when omitted. Allowed: general, fenxiao, boutiquefenxiao Default: general |
isvBizType | string | optional | Cross-border business type. Allowed: cross, cross_daigou, cross_distribution Default: cross |
message | string | optional | Message value used by this API operation. |
outOrderId | string | optional | Out order id value used by this API operation. |
shopPromotionId | string | optional | Shop promotion id value used by this API operation. |
tradeType | string | optional | Trade type: assureTrade, alipay, period, assure, creditBuy, bank, 631staged or 37staged. |
useBorderLogisticsSolution | boolean | optional | Whether to use a cross-border logistics solution. |
useRedEnvelope | string | optional | Use red envelope value used by this API operation. Allowed: y, n Default: n |
Any of option 1 — requires addressId
Any of option 2 — requires addressParam
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.code | string | optional | Upstream business code. |
data.message | string | optional | Message value used by this API operation. |
data.orderId | string | optional | Exact positive integer identifier. Send as a JSON string. Pattern: ^[1-9][0-9]*$ |
data.subCode | string | optional | Sub code value used by this API operation. |
data.subMessage | string | optional | Sub message value used by this API operation. |
data.success | boolean | optional | Inspect this business outcome even when HTTP status is 200. |
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
Use my selected cargoParamList [CARGO_ITEMS] and delivery address [ADDRESS_ID] to prepare a 1688 order. Show the items and address for my review; only after my separate explicit confirmation send confirmCreateOrder=true. Return the actual orderId or upstream error.
Suggested Steps
Review the selected cargo and delivery address with the user. Submit only after separate explicit confirmation with confirmCreateOrder=true, then inspect the returned orderId or upstream error.
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.