1688 Procurement
1688 Authorize URL MCP
Generate a 1688 authorization link to connect your store and enable procurement requests. Use your Nexscope API key to manage the store connection.
1688 Authorize URL 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. Connect A 1688 Store
Prompt: Create an authorization link for my 1688 account named [ACCOUNT_NAME]. Show me the returned authorizeUrl so I can open it and complete authorization myself; do not claim that the store is connected yet.
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.
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_authorize_urlhttps://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-authorize-url-1",
"method": "tools/call",
"params": {
"name": "nexscope_data_alibaba1688_authorize_url",
"arguments": {
"accountName": "My 1688 account"
}
}
}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 |
|---|---|---|---|
accountName | string | required | Display name for this authorization. Example: My 1688 account |
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.authorizeUrl | string | optional | Open manually to authorize. Never expose tokens. |
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. |
Format Illustration
Illustrative example with fictional data, not a live tool call.
Illustrative Question
Create an authorization link for my 1688 account named [ACCOUNT_NAME]. Show me the returned authorizeUrl so I can open it and complete authorization myself; do not claim that the store is connected yet.
Illustrative Response Explanation
Provide your own accountName. The tool returns an authorizeUrl; you must open it and complete authorization manually, then separately verify that the store is ACTIVE and unexpired.
About this sample: This is an illustrative documentation example, not a live response from your account. Check the actual returned fields and status.
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
Illustrative example with fictional data, not a live tool call.
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-authorize-url-example",
"method": "tools/call",
"params": {
"name": "nexscope_data_alibaba1688_authorize_url",
"arguments": {
"accountName": "My 1688 account"
}
}
}MCP Response Format
{
"jsonrpc": "2.0",
"id": "1688-authorize-url-example",
"result": {
"content": [
{
"type": "text",
"text": "{\"code\":0,\"cost\":\"0\",\"data\":{\"authorizeUrl\":\"https://auth.1688.com/example\"},\"msg\":null,\"time\":\"2026-10-20T00:00:00Z\",\"traceId\":null,\"ts\":\"0\"}"
}
],
"structuredContent": {
"code": 0,
"cost": "0",
"data": {
"authorizeUrl": "https://auth.1688.com/example"
},
"msg": null,
"time": "2026-10-20T00:00:00Z",
"traceId": null,
"ts": "0"
},
"isError": false
}
}