1688 Procurement
1688 Invoice Apply MCP
Apply for an invoice for eligible 1688 orders and review the result for each order. Requires an active 1688 authorization and your Nexscope API key.
1688 Invoice Apply 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. Apply For Invoices After Confirmation
Prompt: Using my invoiceApplyModelList [INVOICE_REQUESTS], show the orders and invoice details for my review. After my separate explicit confirmation, send confirmApplyInvoice=true and report both successful and failed orders.
2. Review Partial Invoice Failures
Prompt: After I confirm an invoice application for [INVOICE_REQUESTS], report each order in the returned failedList with its errorCode and errorDesc. Do not assume that every requested order succeeded.
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_invoice_applyhttps://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-invoice-apply-1",
"method": "tools/call",
"params": {
"name": "nexscope_data_alibaba1688_invoice_apply",
"arguments": {
"confirmApplyInvoice": false,
"invoiceApplyModelList": [
{
"amount": 840,
"invoiceType": "VATAX_COMM",
"orderId": "3309156590237728779",
"purchaserInvoiceTitleModel": {
"title": "Example recipient",
"titleType": "PERSONAL"
}
}
]
}
}
}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 |
|---|---|---|---|
confirmApplyInvoice | boolean | required | Must be JSON true after separate explicit user confirmation. Examples default to false and do not authorize this action. Default: false |
invoiceApplyModelList | array | required | invoiceApplyModelList Minimum items: 1 |
invoiceApplyModelList[] | object | required | invoiceApplyModelList |
invoiceApplyModelList[].amount | integer | required | Positive integer cents copied unchanged from invoiceAmount (64-bit integer). Minimum: 1 Maximum: 9223372036854776000 |
invoiceApplyModelList[].invoiceType | string | required | Invoice type value used by this API operation. Allowed: VATAX_COMM, VATAX_SPEC |
invoiceApplyModelList[].orderId | string | required | Exact positive integer identifier. Send as a JSON string. Pattern: ^[1-9][0-9]*$ |
invoiceApplyModelList[].purchaserInvoiceTitleModel | object | required | COMPANY requires taxpayerIdentify. COMPANY with VATAX_SPEC also requires bankName, bankAccountId, registerAddress and registerPhone. |
invoiceApplyModelList[].purchaserInvoiceTitleModel.bankAccountId | string | optional | Required for COMPANY titles with VATAX_SPEC. |
invoiceApplyModelList[].purchaserInvoiceTitleModel.bankName | string | optional | Required for COMPANY titles with VATAX_SPEC. |
invoiceApplyModelList[].purchaserInvoiceTitleModel.registerAddress | string | optional | Required for COMPANY titles with VATAX_SPEC. |
invoiceApplyModelList[].purchaserInvoiceTitleModel.registerPhone | string | optional | Required for COMPANY titles with VATAX_SPEC. |
invoiceApplyModelList[].purchaserInvoiceTitleModel.taxpayerIdentify | string | optional | Required for all COMPANY titles. |
invoiceApplyModelList[].purchaserInvoiceTitleModel.title | string | required | Title value used by this API operation. |
invoiceApplyModelList[].purchaserInvoiceTitleModel.titleType | string | required | Title type value used by this API operation. Allowed: PERSONAL, COMPANY |
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.failedList | array | optional | Failed list value used by this API operation. |
data.failedList[] | object | required | Item in data failedList. |
data.failedList[].errorCode | string | optional | Error code value used by this API operation. |
data.failedList[].errorDesc | string | optional | Error desc value used by this API operation. |
data.failedList[].orderId | string | optional | Exact positive integer identifier. Send as a JSON string. Pattern: ^[1-9][0-9]*$ |
data.failedList[].outBizId | string | optional | Out biz id value used by this API operation. |
data.failedList[].result | string | optional | Result value used by this API operation. |
data.failedList[].tradeOrderCompleted | boolean | optional | Trade order completed value used by this API operation. |
data.message | string | optional | Message value used by this API operation. |
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. |
data.successList | array | optional | Success list value used by this API operation. |
data.successList[] | object | required | Item in data successList. |
data.successList[].errorCode | string | optional | Error code value used by this API operation. |
data.successList[].errorDesc | string | optional | Error desc value used by this API operation. |
data.successList[].orderId | string | optional | Exact positive integer identifier. Send as a JSON string. Pattern: ^[1-9][0-9]*$ |
data.successList[].outBizId | string | optional | Out biz id value used by this API operation. |
data.successList[].result | string | optional | Result value used by this API operation. |
data.successList[].tradeOrderCompleted | boolean | optional | Trade order completed 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
Using my invoiceApplyModelList [INVOICE_REQUESTS], show the orders and invoice details for my review. After my separate explicit confirmation, send confirmApplyInvoice=true and report both successful and failed orders.
Suggested Steps
Review the invoice requests with the user, obtain separate explicit confirmation, then send confirmApplyInvoice=true. Check the returned successful and failed order lists individually.
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.