Find And Manage Pricing Plan Orders

The calls need the Wix Pricing Plans app on the site (appDefId 1522827f-c56c-a5c9-2ac9-00f9e6ae12d3). To create, rename or reprice the plans themselves, use Create and Update Pricing Plans.

Step 1: List the orders

List Orders (opens in a new tab): GET https://www.wixapis.com/pricing-plans/v2/orders. Use this method, not the member-facing List Orders (/pricing-plans/v2/member/orders), which returns 403 for the site owner.

All filters are query parameters:

Write enum values in upper case, and repeat a parameter once per value: orderStatuses=ACTIVE&orderStatuses=PAUSED. A comma-joined list (orderStatuses=ACTIVE,PAUSED) or a lower-case value returns 400 Failed to parse JSON. Different parameters combine with AND.

There is no date filter. For purchases in a period, sort on createdDate DESC and stop at the start of the period; for end dates, read every page and compare endDate in code (Step 3). Without sorting, the orders do not come back in date order.

Active orders of one plan, newest first:

The response holds orders[] and pagingMetadata (count, offset, hasNext; no total). While hasNext is true, send the same request with offset raised by 50. A count or a report needs every page.

The plan ID from its name. List the plans with Query Plans (opens in a new tab) and match name in code, ignoring case (the API matches names case-sensitively). Archived plans are returned too and still have orders:

The plans are in plans[], each with id, name and archived. Several plans fit the user’s words: ask which one. Every order also holds planName, the plan’s name at the time of purchase.

One order: GET https://www.wixapis.com/pricing-plans/v2/orders/<order id> returns order.

The fields of an order

Step 2: Get the buyers’ names and emails

Send the buyers’ buyer.contactId values to Query Contacts (opens in a new tab), up to 100 per request:

Each contact in contacts[] has id, info.name.first, info.name.last and primaryInfo.email. Match them to the orders on id = buyer.contactId.

The orders of one buyer. buyerIds takes member IDs.

• The user gives an email: find the member with Query Members (Step 5) and send its id as buyerIds.
• The user gives a name: find the contact with Query Contacts and { "filter": { "info.name.first": "Sam", "info.name.last": "Chen" } } (case-insensitive). Then list the orders, of the plan when the user names one, and keep those whose buyer.contactId is the contact’s id. Several contacts match: ask the user which one.

Step 3: Build the answer

Leave out DRAFT orders in every answer: they are abandoned checkouts (an offline order also shows DRAFT for a second or two after it is created). Give dates in the site’s time zone, properties.timeZone from GET https://www.wixapis.com/site-properties/v4/properties.

• Who bought a plan, and when: the plan’s orders with every status except DRAFT. Give each buyer’s name, email, createdDate as the purchase date, and status.
• New purchases in the last N days: sort on createdDate DESC, and read pages until an order’s createdDate is older than the start of the period. Keep the orders inside it. Recorded offline orders can carry an earlier startDate; the purchase date is still createdDate.
• How many active subscribers: orderStatuses=ACTIVE, every page. Count distinct buyer.contactId, because one person can hold several orders, and say whether the number is people or orders. Give PAUSED and PENDING orders as separate numbers when there are any. Do not filter on autoRenewCanceled=false for this: one-time plans have no auto-renewal and drop out of that filter.
• Ending in the next N days: read the ACTIVE orders and keep those whose endDate falls in the period. Do not rely on sorting by endDate: orders without one come first in ASC order. An order without endDate renews; its next payment date is currentCycle.endedDate. Report that date when the user asks about renewals or payments due.
• Set to cancel: ACTIVE orders whose cancellation.effectiveAt is NEXT_PAYMENT_DATE; they end on endDate.
• Current and former customers: current = ACTIVE, PAUSED or PENDING; former = ENDED or CANCELED. A person with both kinds of order is a current customer. Find the emails with Step 2.
• Unpaid orders: paymentStatuses=UNPAID. Online payments update this field by themselves; an offline order stays UNPAID until the owner marks it paid.
• 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 (plan, status, period), and offer the plan’s orders of every status.

Step 4: Change an order

A request that names the buyer or the order and the change (“pause Dana’s Gold membership”, “extend John’s pass to 30 June”) is already the user’s confirmation. Ask first when several orders fit (one buyer with two orders of the plan), and before a change to more than one order, with their number. For a cancellation the user did not time, ask whether it is now or at the end of the paid period.

Every change returns {}, which means it was accepted. The order shows the change in a read one or two seconds later. Read it with Get Order before you report the result. If the read does not show the change yet, read up to two more times; if it still does not show, report what the last read shows. Do not send the change again.

After a cancel at NEXT_PAYMENT_DATE, the order stays ACTIVE: it gets autoRenewCanceled: true, a cancellation, and an endDate at the end of the paid cycle, when its status becomes CANCELED. That is the expected result; do not cancel again with IMMEDIATELY. A cancel IMMEDIATELY sets status to CANCELED and endDate to now.

A 409 INVALID_REVISION from Mark as Paid on an order created a few seconds earlier can still have marked it paid. Read the order before you send it again.

No API method changes an order’s start date or its payment date: tell the user so instead of searching for one. The owner can move the payment date of an active recurring subscription in the dashboard; give them the steps in Changing the Payment Date for Recurring Subscriptions (opens in a new tab), and a link from Pricing Plans Dashboard Navigation.

Step 5: Record a manual (offline) order

Use Create Offline Order (opens in a new tab) when the buyer paid outside the site (cash, bank transfer), still owes an offline payment, or gets the plan from the owner for free. A request that names the buyer and the plan is the confirmation. Purchase limits of the plan do not apply to offline orders.

1. Find the buyer’s member ID by email with Query Members (opens in a new tab) (the match ignores case):

   bashCopy

   curl -X POST 'https://www.wixapis.com/members/v1/members/query' \
   -H 'Content-Type: application/json' \
   -H 'Authorization: <AUTH>' \
   -d '{ "query": { "filter": { "loginEmail": "jane@example.com" } }, "fieldsets": ["FULL"] }'

   The member is members[0]; take its id. With "fieldsets": ["FULL"] it also holds loginEmail, contactId and contact.firstName / contact.lastName; without it, the member comes back with no email and no name. A member created a few seconds earlier is not found yet: when the result is empty, send the same query once more after a few seconds. Still no member has that email: ask the user before you create one with Create Member (opens in a new tab): POST https://www.wixapis.com/members/v1/members with { "member": { "loginEmail": "jane@example.com", "contact": { "firstName": "Jane", "lastName": "Doe" } } }, then use member.id.

2. Find the plan ID with Query Plans (Step 1).

3. Create the order:

   bashCopy

   curl -X POST 'https://www.wixapis.com/pricing-plans/v2/checkout/orders/offline' \
   -H 'Content-Type: application/json' \
   -H 'Authorization: <AUTH>' \
   -d '{ "planId": "<plan id>", "memberId": "<member id>", "paid": true }'

   memberId takes the member ID, not a contact ID. Send paid: true when the buyer paid outside the site or the owner gives a paid plan for free, because nothing is owed. Leave it out only when the buyer still owes the payment; mark the order paid later. A free plan needs no paid. startDate (for example "2026-12-01T00:00:00.000Z") is optional and defaults to now; a future date makes the order PENDING.

The response holds order.id. Its status and lastPaymentStatus can still show DRAFT, UNDEFINED or UNPAID for a second or two; read the order with Get Order before you report them.

On sites where plans are sold through Wix eCommerce (the order has onEcom: true), every plan order also creates an eCommerce order with the plan name as its line item. Report subscription state (active, paused, cancelled, ending) from the plan orders here: the eCommerce order keeps status APPROVED after the plan order is cancelled.