Find and Report on Orders

Reads orders with Search Orders. Every call here is read-only. Orders from Wix Stores, Bookings, Events and other Wix apps that sell through eCommerce all come back from the same endpoint.

To change an order after finding it (fulfil, refund, cancel, edit), use the method for that action in the Orders API, and confirm the change with the user first.

Step 1: Pick the filter

Search Orders accepts filters on a closed list of fields. Use these:

These filters are rejected with 400 Unknown token, although the method schema lists them: billingInfo.contactDetails.firstName, billingInfo.contactDetails.lastName and priceSummary.total.amount. To find orders by the buyer's name, find the contact first and filter on its ID (below). To find orders by their total, read the orders and filter them in code. For a partial product name ("the cap"), find the product first with Find Products and filter by its ID.

Buyer by name. Find the contact with Query Contacts, then filter orders on buyerInfo.contactId:

The contacts are in contacts[], each with id, info.name.first, info.name.last and primaryInfo.email. Several contacts match: ask the user which one. None matches: read the orders and match billingInfo.contactDetails.firstName and lastName in code.

Use purchasedDate for periods, not createdDate. They are the same for checkout orders, but createdDate is when the order record was created, so it is wrong for orders added later with a past purchase date.

Step 2: Search

POST https://www.wixapis.com/ecom/v1/orders/search

One order by its number:

Orders purchased in October 2026, oldest first. Set the bounds at midnight in the site's time zone, converted to UTC; the time zone is properties.timeZone (for example America/New_York) from GET https://www.wixapis.com/site-properties/v4/properties. The example uses UTC midnight:

Unpaid orders of one buyer that contain a product:

The response holds orders and metadata. Without a sort, the newest createdDate comes first.

Paging. cursorPaging.limit is at most 100. While metadata.hasNext is true, send the next request with only cursorPaging, holding the same limit and metadata.cursors.next. The cursor carries the filter and the sort of the first request; a filter sent with a cursor is ignored.

A report needs every page. Stop only when hasNext is false.

What is left out. Without a status filter, orders with status PENDING or REJECTED are not returned. Orders with status INITIALIZED are never returned; read one with Get Order (GET https://www.wixapis.com/ecom/v1/orders/<orderId>). Cancelled orders are returned, so exclude "status": "CANCELED" from sales totals unless the user asks for them. An order placed a few seconds ago can be missing from the results until the search index catches up; when you hold its ID, read it with Get Order.

Step 3: Read the fields

Amounts in priceSummary.total include shipping and tax; priceSummary.subtotal is the items only.

The order does not hold payment methods. For those, send the order IDs to List Transactions For Multiple Orders:

The response has one entry per order in orderTransactions[], with orderId and payments[]. The method of a payment is payments[].regularPaymentDetails.paymentMethodName.siteLanguageName (for example "Credit/Debit Cards"); a gift card payment has giftcardPaymentDetails instead. An order with no recorded payment has an empty payments list.

Step 4: Build the answer

• One order: give its number, date, status, payment and fulfillment status, items with quantities, and total with currency. Add the dashboard link from Stores Dashboard Navigation when the user needs to act on it.
• Units sold per product: read every page for the period, skip orders with status CANCELED, and add up lineItems[].quantity per productName.original (or per catalogItemId when names can repeat).
• Revenue for a period: add up priceSummary.total.amount of the orders with paymentStatus PAID whose status is not CANCELED. List the orders with any other paymentStatus (such as NOT_PAID, PENDING, PARTIALLY_PAID, PARTIALLY_REFUNDED, FULLY_REFUNDED) on one line per status, with their count and total, and leave them out of the revenue figure. Say that the figure includes shipping and tax, and give the subtotal sum too when the user asks for sales before shipping and tax. Amounts are strings: convert them to numbers before adding, and do not add amounts in different currency values.
• Per customer: group by buyerInfo.email, and take the name from billingInfo.contactDetails.
• Exports: return the rows with the columns the user asked for. A list longer than a few dozen rows goes in a file or a table, not in a chat message.

No orders found: say so with the filter you used (number, period or buyer), and offer the most recent orders instead.