Get order count
GET/openapi/2026-07/orders/count
Provides the total number of orders matching the specified query parameters.
Request
Query Parameters
- opened: pending payment.
- cancelled: cancelled.
- placed: in progress.
- finished: completed. Example: ?status=opened&status=finished
- initialled: initial.
- waiting: waiting to ship.
- partially_shipped: partially shipped.
- shipped: fully shipped.
- partially_finished: partially received.
- finished: fully received.
- cancelled: cancelled.
- returning: return in progress.
- partially_returned: partially returned.
- returned: fully returned. Example: ?fulfillment_status=waiting&fulfillment_status=shipped
- waiting: pending payment.
- paying: payment under review.
- authorized: authorized.
- partially_paid: partially paid.
- paid: paid.
- cancelled: cancelled.
- failed: payment failed.
- refunding: refund in progress.
- refund_failed: refund failed.
- refunded: fully refunded.
- partially_refunded: partially refunded. Example: ?financial_status=waiting&financial_status=paid
- true: apply filter.
- false: do not apply filter.
name: customer name (not recipient name)number: order numberid: order IDsku: product SKU (snapshot data). For exact match useskusspu: product SPU (snapshot data). For exact match usespustag_list: order tags. For exact match useorder_tagsshipping_email: shipping address email. For exact match useshipping_emailsshipping_phone: shipping address phone. For exact match useshipping_phonesbrowser_ip: order IP address. For exact match usebrowser_ipsproduct_tags: product tags (snapshot data)product_title: product title (snapshot data)credit_card_number: last 4 digits of the payment cardsource: first-visit landing pagesource_name: first-visit sourcetracking_number: shipping tracking numbershipping_line_name: shipping plan nameline_item_vendor: product vendordiscount_code: discount codeshipping_address_extra_info: special shipping field infotransaction_id: payment transaction numbercustomer_id: customer IDlast_landing_url: last-visit landing pagelast_referrer_show: last-visit sourcecountry: country name (snapshot data; mixed CN/EN search not supported)shop_name: POS shop namestaff_contact: POS staff Note: for fields that also have a dedicated exact-match array parameter (sku/spu/tag_list/shipping_email/shipping_phone/browser_ip), use the array parameter for full-value lookups; reserve fuzzy mode for prefix or fragment search. Example: ?fuzzy_fields=name&fuzzy_fields=number
Filter orders by order IDs. Example: ?ids=1001&ids=1002
Filter by order status.
Filter by order fulfillment status.
Filter by payment status.
Filter orders by cart recovery status. Example: ?recovery_status=value1&recovery_status=value2
Filter orders by location ID
Keyword for searching orders
Fields to apply keyword search on. Supported values: order_no, email, phone, name, etc. Example: ?keyword_scope_fields=order_no&keyword_scope_fields=email
Filter orders by customer ID
Filter orders with total greater than or equal to this value
Filter orders with total less than or equal to this value
Filter orders created after this time (e.g., 2018-11-02T12:30:10Z)
Filter orders created before this time (e.g., 2018-11-02T12:30:10Z)
Filter orders updated after this time (e.g., 2018-11-02T12:30:10Z)
Filter orders updated before this time (e.g., 2018-11-02T12:30:10Z)
Filter orders placed after this time (e.g., 2018-11-02T12:30:10Z)
Filter orders placed before this time (e.g., 2018-11-02T12:30:10Z)
Filter orders by sales channel. Example: ?sales_platform=value1&sales_platform=value2
Apply the same has_filter logic as the admin-side incomplete order list.
Filter orders finished after this time (e.g., 2018-11-02T12:30:10Z)
Filter orders finished before this time (e.g., 2018-11-02T12:30:10Z)
Filter orders fulfilled after this time (e.g., 2018-11-02T12:30:10Z)
Filter orders fulfilled before this time (e.g., 2018-11-02T12:30:10Z)
Filter orders by last touchpoint time start (e.g., 2018-11-02T12:30:10Z)
Filter orders by last touchpoint time end (e.g., 2018-11-02T12:30:10Z)
Filter orders by first touchpoint time start (e.g., 2018-11-02T12:30:10Z)
Filter orders by first touchpoint time end (e.g., 2018-11-02T12:30:10Z)
Filter orders by shipping address email. Example: ?shipping_emails=[email protected]&shipping_emails=[email protected]
Filter orders by shipping address phone. Example: ?shipping_phones=13800000001&shipping_phones=13800000002
Filter orders by browser IP address. Example: ?browser_ips=1.2.3.4&browser_ips=5.6.7.8
Filter orders by product ID. Example: ?product_ids=2001&product_ids=2002
Filter orders by SKU. Example: ?skus=SKU0001&skus=SKU0002
Filter orders by SPU. Example: ?spus=SPU0001&spus=SPU0002
Filter orders by order tag. Example: ?order_tags=vip&order_tags=new
Filter orders by customer email. Example: ?customer_emails=[email protected]&customer_emails=[email protected]
Field names to apply fuzzy matching on. Combined with fuzzy_keywords / fuzzy_relation Allowed values:
Fuzzy keyword list. Any keyword matches in any of fuzzy_fields counts as a hit. Example: ?fuzzy_keywords=iphone&fuzzy_keywords=vip
How fuzzy_fields entries are joined: "and" or "or". Defaults to "or"
Responses
- 200
OK
- application/json
- Schema
- Example
Schema
error code
error message
data object
Total count of orders matching the filter conditions
{
"code": "string",
"message": "string",
"data": {
"count": 0
}
}