---
title: "Luckin Coffee"
description: "Official Luckin Coffee store search, drink selection and pickup orders. Creating or cancelling an order requires exact human approval. Pay through Luckin when payment is required."
---

> Documentation Index
> Fetch the complete documentation index at: https://help.tooluse.net/llms.txt
> Use this file to discover all available pages before exploring further.

# Luckin Coffee

<p>Official Luckin Coffee store search, drink selection and pickup orders. Creating or cancelling an order requires exact human approval.</p>

<h2>Example workflows</h2>

<p>Copy a prompt into your connected AI client after connecting this integration. Choose resources you can access and review the supported command before running it.</p>

<h3>Find Luckin stores</h3>

<pre><code class="language-text" data-workflow-prompt>Help me with this task in Luckin Coffee: Find Luckin stores. Ask me for any required inputs and confirm the resources and scope before calling the command. Read one response page. Turn the returned data into a concise working summary with original IDs, dates and source links when available. Separate missing information from confirmed results and tell me whether more pages remain. Do not invent fields or change data.</code></pre>
<p><a href="https://tooluse.net/tools/integrations/luckin-coffee?command=luckin.shops.list">Explore this command: luckin.shops.list</a></p>

<h3>Find Luckin drinks</h3>

<pre><code class="language-text" data-workflow-prompt>Help me with this task in Luckin Coffee: Find Luckin drinks. Ask me for any required inputs and confirm the resources and scope before calling the command. Read one response page. Turn the returned data into a concise working summary with original IDs, dates and source links when available. Separate missing information from confirmed results and tell me whether more pages remain. Do not invent fields or change data.</code></pre>
<p><a href="https://tooluse.net/tools/integrations/luckin-coffee?command=luckin.products.search">Explore this command: luckin.products.search</a></p>

<details data-command-index><summary>What you can do (8)</summary>
<h2>What you can do</h2>
<p>Available commands: 8 (6 read, 2 write). Enable only the commands your application needs.</p>
<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Command</th>
<th>Effect</th>
</tr>
</thead>
<tbody><tr>
<td><a href="https://help.tooluse.net/integrations/luckin-coffee#command-luckin-shops-list">Find Luckin stores</a> — <code>luckin.shops.list</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/luckin-coffee#command-luckin-products-search">Find Luckin drinks</a> — <code>luckin.products.search</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/luckin-coffee#command-luckin-products-switch">Change drink options</a> — <code>luckin.products.switch</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/luckin-coffee#command-luckin-products-get">Read Luckin drink details</a> — <code>luckin.products.get</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/luckin-coffee#command-luckin-orders-preview">Preview a Luckin order and discounts</a> — <code>luckin.orders.preview</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/luckin-coffee#command-luckin-orders-create">Create a Luckin pickup order</a> — <code>luckin.orders.create</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/luckin-coffee#command-luckin-orders-get">Read a Luckin order and pickup code</a> — <code>luckin.orders.get</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/luckin-coffee#command-luckin-orders-cancel">Cancel a Luckin order</a> — <code>luckin.orders.cancel</code></td>
<td>Write</td>
</tr>
</tbody></table>
</div>
</details>
<h2>Connect and use</h2>

<p><a href="https://tooluse.net/tools/integrations/luckin-coffee?connect=own">Connect and use</a></p>
<p>This connection uses your provider account.</p>
<p>Connect this integration, enter your provider credentials, choose commands and save. Complete provider authorization if prompted.</p>
<h2>Get your provider credentials</h2>
<p>Follow these steps for Luckin Coffee, then enter the issued values in the connection form below.</p>
<ol>
<li>Get an MCP access token from the official Luckin Coffee open platform and enter it in your connection. Start with a store or product read. Enable read-write access only when you intend to create or cancel an order, and approve the exact order before submission. Provider charges apply.</li>
</ol>
<p><a href="https://open.lkcoffee.com/docs">Official credential setup</a></p>
<h2>Where to enter credentials</h2>
<p>In the integration page, sign in, choose your workspace and open Connect. If a <strong>Credentials</strong> choice is shown, select <strong>Use my credentials</strong>. Fill the following connection fields and save. Provider credentials belong in this form, never in an MCP configuration or tool input.</p>
<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Connection field</th>
<th>Requirement</th>
</tr>
</thead>
<tbody><tr>
<td>Application token (leave empty for personal accounts)</td>
<td>Optional</td>
</tr>
<tr>
<td>Access mode</td>
<td>Optional</td>
</tr>
<tr>
<td>Account authorization</td>
<td>Optional</td>
</tr>
</tbody></table>
</div><p>Open API keys and create a Tooluse.net key for the enabled commands.</p>
<p>Set TOOLUSE_API_KEY in your client and use the shared MCP configuration.</p>
<p><a href="https://help.tooluse.net/clients">Configure Claude Code, Codex or Cursor once</a></p>

<h2>Permissions and results</h2>

<p>If you have more than one workspace, check the selected workspace in the connection or API-key dialog before saving. Roles, enabled commands, expiry and revocation use Tooluse.net&#39;s existing permissions. Disabling a connection or revoking a key immediately prevents new calls.</p>

<p>Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.</p>

<p>Your connection&#39;s daily allowance and key permissions also apply. Adding a connection does not make a provider request.</p>

<p>Calls return the shared execution receipt and a Claude tool_result. Provider output varies by operation; consult the provider documentation for its response fields. Unconfirmed calls should be checked before retrying.</p>

<h2>Call from your client</h2>

<p>Use the shared MCP configuration. Refresh your client&#39;s tool list after saving the connection or changing key permissions, then call the returned tool name with the example input below.</p>

<p><a href="https://help.tooluse.net/clients">Configure Claude Code, Codex or Cursor once</a></p>

<h2>Discover your enabled tools</h2>

<p>List permitted tools in Claude format. Read every page using page and size (maximum 100) until all results have been received. Use the returned name, not a catalog capability identifier, in the tool_use block.</p>

<pre><code class="language-bash">curl 'https://api.tooluse.net/v1/tools' \
  -H "Authorization: Bearer $TOOLUSE_API_KEY"
</code></pre>

<p>Find this command in the tool list permitted by your key. Replace svc_FROM_YOUR_TOOL_LIST with its returned name. Use a new Idempotency-Key for each new call and retain it when retrying that same call.</p>

<h2>HTTP call</h2>

<pre><code class="language-bash">curl 'https://api.tooluse.net/v1/tool-calls' \
  -H "Authorization: Bearer $TOOLUSE_API_KEY" \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: replace-with-a-new-call-id' \
  --data '{
  "type": "tool_use",
  "id": "toolu_example",
  "name": "svc_FROM_YOUR_TOOL_LIST",
  "input": {
    "longitude": 116.392435,
    "latitude": 39.982376
  }
}'
</code></pre>

<p>Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.</p>

<h2>Commands</h2>

<details id="command-luckin-shops-list">
<summary><span>Find Luckin stores — <code>luckin.<wbr>shops.<wbr>list</code></span></summary>
<p>Run Find Luckin stores with Luckin Coffee. This is a read command; it does not grant access beyond the connected account's permissions.</p>
<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://tooluse.net/tools/integrations/luckin-coffee?connect=own&amp;command=luckin.shops.list">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>longitude</code></td>
<td>number</td>
<td>Required</td>
<td>Longitude</td>
<td><code>minimum: -180; maximum: 180</code></td>
</tr>
<tr>
<td><code>latitude</code></td>
<td>number</td>
<td>Required</td>
<td>Latitude</td>
<td><code>minimum: -90; maximum: 90</code></td>
</tr>
<tr>
<td><code>deptName</code></td>
<td>string</td>
<td>Optional</td>
<td>Store name</td>
<td><code>minLength: 1; maxLength: 200; pattern: &quot;^[^\\p{C}]+$&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/luckin-coffee/commands/luckin.shops.list">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "longitude": 116.392435,
  "latitude": 39.982376
}
</code></pre>

<p>At most 3 provider requests per invocation; timeout: 15 seconds.</p>

</details>
<details id="command-luckin-products-search">
<summary><span>Find Luckin drinks — <code>luckin.<wbr>products.<wbr>search</code></span></summary>
<p>Run Find Luckin drinks with Luckin Coffee. This is a read command; it does not grant access beyond the connected account's permissions.</p>
<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://tooluse.net/tools/integrations/luckin-coffee?connect=own&amp;command=luckin.products.search">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>deptId</code></td>
<td>integer</td>
<td>Required</td>
<td>Store ID</td>
<td><code>minimum: 1; maximum: 9007199254740991</code></td>
</tr>
<tr>
<td><code>query</code></td>
<td>string</td>
<td>Required</td>
<td>Drink request</td>
<td><code>minLength: 1; maxLength: 1000; pattern: &quot;^[^\\p{C}]+$&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/luckin-coffee/commands/luckin.products.search">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "deptId": 245062453,
  "query": "Iced latte"
}
</code></pre>

<p>At most 3 provider requests per invocation; timeout: 15 seconds.</p>

</details>
<details id="command-luckin-products-switch">
<summary><span>Change drink options — <code>luckin.<wbr>products.<wbr>switch</code></span></summary>
<p>Run Change drink options with Luckin Coffee. This is a read command; it does not grant access beyond the connected account's permissions.</p>
<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://tooluse.net/tools/integrations/luckin-coffee?connect=own&amp;command=luckin.products.switch">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>deptId</code></td>
<td>integer</td>
<td>Required</td>
<td>Store ID</td>
<td><code>minimum: 1; maximum: 9007199254740991</code></td>
</tr>
<tr>
<td><code>productId</code></td>
<td>integer</td>
<td>Required</td>
<td>Product ID</td>
<td><code>minimum: 1; maximum: 9007199254740991</code></td>
</tr>
<tr>
<td><code>skuCode</code></td>
<td>string</td>
<td>Required</td>
<td>SKU code</td>
<td><code>minLength: 1; maxLength: 200; pattern: &quot;^[^\\p{C}]+$&quot;</code></td>
</tr>
<tr>
<td><code>attrOperationParam</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>attrOperationParam.attributeId</code></td>
<td>integer</td>
<td>Required</td>
<td>Attribute group ID</td>
<td><code>minimum: 1; maximum: 9007199254740991</code></td>
</tr>
<tr>
<td><code>attrOperationParam.subAttr</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>attrOperationParam.subAttr.attributeId</code></td>
<td>integer</td>
<td>Required</td>
<td>Attribute value ID</td>
<td><code>minimum: 1; maximum: 9007199254740991</code></td>
</tr>
<tr>
<td><code>attrOperationParam.subAttr.operation</code></td>
<td>integer</td>
<td>Required</td>
<td></td>
<td><code>const: 3</code></td>
</tr>
<tr>
<td><code>amount</code></td>
<td>integer</td>
<td>Required</td>
<td>Quantity</td>
<td><code>minimum: 1; maximum: 20</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/luckin-coffee/commands/luckin.products.switch">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "deptId": 245062453,
  "productId": 123,
  "skuCode": "example-sku",
  "amount": 1,
  "attrOperationParam": {
    "attributeId": 1,
    "subAttr": {
      "attributeId": 2,
      "operation": 3
    }
  }
}
</code></pre>

<p>At most 3 provider requests per invocation; timeout: 15 seconds.</p>

</details>
<details id="command-luckin-products-get">
<summary><span>Read Luckin drink details — <code>luckin.<wbr>products.<wbr>get</code></span></summary>
<p>Run Read Luckin drink details with Luckin Coffee. This is a read command; it does not grant access beyond the connected account's permissions.</p>
<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://tooluse.net/tools/integrations/luckin-coffee?connect=own&amp;command=luckin.products.get">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>deptId</code></td>
<td>integer</td>
<td>Required</td>
<td>Store ID</td>
<td><code>minimum: 1; maximum: 9007199254740991</code></td>
</tr>
<tr>
<td><code>productId</code></td>
<td>integer</td>
<td>Required</td>
<td>Product ID</td>
<td><code>minimum: 1; maximum: 9007199254740991</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/luckin-coffee/commands/luckin.products.get">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "deptId": 245062453,
  "productId": 123
}
</code></pre>

<p>At most 3 provider requests per invocation; timeout: 15 seconds.</p>

</details>
<details id="command-luckin-orders-preview">
<summary><span>Preview a Luckin order and discounts — <code>luckin.<wbr>orders.<wbr>preview</code></span></summary>
<p>Run Preview a Luckin order and discounts with Luckin Coffee. This is a read command; it does not grant access beyond the connected account's permissions.</p>
<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://tooluse.net/tools/integrations/luckin-coffee?connect=own&amp;command=luckin.orders.preview">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>deptId</code></td>
<td>integer</td>
<td>Required</td>
<td>Store ID</td>
<td><code>minimum: 1; maximum: 9007199254740991</code></td>
</tr>
<tr>
<td><code>productList</code></td>
<td>array</td>
<td>Required</td>
<td>Products</td>
<td><code>minItems: 1; maxItems: 20</code></td>
</tr>
<tr>
<td><code>productList[]</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>productList[].amount</code></td>
<td>integer</td>
<td>Required</td>
<td>Quantity</td>
<td><code>minimum: 1; maximum: 20</code></td>
</tr>
<tr>
<td><code>productList[].productId</code></td>
<td>integer</td>
<td>Required</td>
<td>Product ID</td>
<td><code>minimum: 1; maximum: 9007199254740991</code></td>
</tr>
<tr>
<td><code>productList[].skuCode</code></td>
<td>string</td>
<td>Required</td>
<td>SKU code</td>
<td><code>minLength: 1; maxLength: 200; pattern: &quot;^[^\\p{C}]+$&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/luckin-coffee/commands/luckin.orders.preview">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "deptId": 245062453,
  "productList": [
    {
      "productId": 123,
      "skuCode": "example-sku",
      "amount": 1
    }
  ]
}
</code></pre>

<p>At most 3 provider requests per invocation; timeout: 15 seconds.</p>

</details>
<details id="command-luckin-orders-create">
<summary><span>Create a Luckin pickup order — <code>luckin.<wbr>orders.<wbr>create</code></span></summary>
<p>Run Create a Luckin pickup order with Luckin Coffee. This command can change provider data. Review the target and input before invoking it.</p>
<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://tooluse.net/tools/integrations/luckin-coffee?connect=own&amp;command=luckin.orders.create">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>deptId</code></td>
<td>integer</td>
<td>Required</td>
<td>Store ID</td>
<td><code>minimum: 1; maximum: 9007199254740991</code></td>
</tr>
<tr>
<td><code>productList</code></td>
<td>array</td>
<td>Required</td>
<td>Products</td>
<td><code>minItems: 1; maxItems: 20</code></td>
</tr>
<tr>
<td><code>productList[]</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>productList[].amount</code></td>
<td>integer</td>
<td>Required</td>
<td>Quantity</td>
<td><code>minimum: 1; maximum: 20</code></td>
</tr>
<tr>
<td><code>productList[].productId</code></td>
<td>integer</td>
<td>Required</td>
<td>Product ID</td>
<td><code>minimum: 1; maximum: 9007199254740991</code></td>
</tr>
<tr>
<td><code>productList[].skuCode</code></td>
<td>string</td>
<td>Required</td>
<td>SKU code</td>
<td><code>minLength: 1; maxLength: 200; pattern: &quot;^[^\\p{C}]+$&quot;</code></td>
</tr>
<tr>
<td><code>longitude</code></td>
<td>number</td>
<td>Required</td>
<td>Longitude</td>
<td><code>minimum: -180; maximum: 180</code></td>
</tr>
<tr>
<td><code>latitude</code></td>
<td>number</td>
<td>Required</td>
<td>Latitude</td>
<td><code>minimum: -90; maximum: 90</code></td>
</tr>
<tr>
<td><code>couponCodeList</code></td>
<td>array</td>
<td>Optional</td>
<td>Coupon codes from the order preview</td>
<td><code>maxItems: 20; uniqueItems: true</code></td>
</tr>
<tr>
<td><code>couponCodeList[]</code></td>
<td>string</td>
<td>Optional</td>
<td>Coupon code</td>
<td><code>minLength: 1; maxLength: 200; pattern: &quot;^[^\\p{C}]+$&quot;</code></td>
</tr>
<tr>
<td><code>remark</code></td>
<td>string</td>
<td>Optional</td>
<td>Order note</td>
<td><code>minLength: 1; maxLength: 500; pattern: &quot;^[^\\p{C}]+$&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/luckin-coffee/commands/luckin.orders.create">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "deptId": 245062453,
  "productList": [
    {
      "productId": 123,
      "skuCode": "example-sku",
      "amount": 1
    }
  ],
  "longitude": 116.392435,
  "latitude": 39.982376
}
</code></pre>

<p>At most 3 provider requests per invocation; timeout: 15 seconds.</p>

</details>
<details id="command-luckin-orders-get">
<summary><span>Read a Luckin order and pickup code — <code>luckin.<wbr>orders.<wbr>get</code></span></summary>
<p>Run Read a Luckin order and pickup code with Luckin Coffee. This is a read command; it does not grant access beyond the connected account's permissions.</p>
<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://tooluse.net/tools/integrations/luckin-coffee?connect=own&amp;command=luckin.orders.get">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>orderId</code></td>
<td>string</td>
<td>Required</td>
<td>Order ID</td>
<td><code>minLength: 1; maxLength: 32; pattern: &quot;^[0-9]{1,32}$&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/luckin-coffee/commands/luckin.orders.get">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "orderId": "1234567890123456789"
}
</code></pre>

<p>At most 3 provider requests per invocation; timeout: 15 seconds.</p>

</details>
<details id="command-luckin-orders-cancel">
<summary><span>Cancel a Luckin order — <code>luckin.<wbr>orders.<wbr>cancel</code></span></summary>
<p>Run Cancel a Luckin order with Luckin Coffee. This command can change provider data. Review the target and input before invoking it.</p>
<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://tooluse.net/tools/integrations/luckin-coffee?connect=own&amp;command=luckin.orders.cancel">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>orderId</code></td>
<td>string</td>
<td>Required</td>
<td>Order ID</td>
<td><code>minLength: 1; maxLength: 32; pattern: &quot;^[0-9]{1,32}$&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/luckin-coffee/commands/luckin.orders.cancel">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "orderId": "1234567890123456789"
}
</code></pre>

<p>At most 3 provider requests per invocation; timeout: 15 seconds.</p>

</details>
<h2>Errors</h2>

<p>Check the key&#39;s expiry, revocation, workspace and allowed operations.</p>

<p>Reuse the same idempotency key only for the same request.</p>

<p>The connection or provider limit has been reached. Check the receipt before retrying.</p>

<h2>Test the connection</h2>

<p>Open the integration&#39;s commands below to inspect parameters and examples. Start with a read command for an account or resource you can access. Refresh your client&#39;s tool list, use the returned tool name, and check the execution result and usage. Provider charges and permissions still apply. Never test a write against production data without reviewing it.</p>

<p><a href="https://open.lkcoffee.com/docs">Official provider documentation</a></p>

Source: https://help.tooluse.net/integrations/luckin-coffee/index.mdx
