Index of every page on this site: llms.txt
All skills
wix avatar

/wix-manage

@e2bc48e official
by Wix.comwix/skills40 stars
42
Run it yourself

REST recipes to configure and manage a Wix site's business solutions — stores, bookings, donations, payments, CMS, and more — and to publish HTML, CSS and JavaScript files as a live Wix site, with or without a Wix account. Open the matching recipe for the exact endpoint, method, and payload before calling — never guess a Wix API, never write Wix dashboard URL from memory. Routes to: automations, stores, bookings, donations, get-paid, CMS, contacts, forms, media, app-installation, custom-apps, pricing-plans, restaurants, ricos rich-content, sites, collaborators, studio-workspace, blog, calendar, domains, events, site-properties, ecommerce, marketing, online-programs, google-ads, google-business-profile, analytics, accessibility, seo, dashboard-navigation.

Use this Skill: https://skilld.dev/gh/wix/skills/wix-manage

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

referencesecommercefind-and-report-on-orders.md

≈2.5k tokens on demand. Your agent reads this file only when SKILL.md points to it.

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:

The user gives Filter
An order number ("order #10003") "number": 10003
A period ("last month", "since 1 October") purchasedDate with $gte and $lt, each in its own condition under $and; one object holding both operators is rejected with 400
A buyer's email "buyerInfo.email": "jane@example.com" (case-insensitive; $startsWith also works)
A buyer's contact ID "buyerInfo.contactId": "<contact id>"
A product's exact name "lineItems.productName.original": { "$hasSome": ["Baseball Cap"] } (case-insensitive, whole name only)
A product's ID "lineItems.catalogReference.catalogItemId": { "$hasSome": ["<product id>"] }
Unpaid orders "paymentStatus": "NOT_PAID" and "status": { "$in": ["APPROVED", "PENDING"] }, so orders still waiting for payment are included
Paid orders "paymentStatus": "PAID"
Orders not shipped yet "fulfillmentStatus": "NOT_FULFILLED"
Cancelled orders "status": "CANCELED"

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:

curl -X POST 'https://www.wixapis.com/contacts/v4/contacts/query' \
-H 'Content-Type: application/json' \
-H 'Authorization: <AUTH>' \
-d '{ "query": { "filter": { "info.name.last": "Chen" } } }'

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:

curl -X POST 'https://www.wixapis.com/ecom/v1/orders/search' \
-H 'Content-Type: application/json' \
-H 'Authorization: <AUTH>' \
-d '{
  "search": {
    "filter": { "number": 10003 }
  }
}'

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:

curl -X POST 'https://www.wixapis.com/ecom/v1/orders/search' \
-H 'Content-Type: application/json' \
-H 'Authorization: <AUTH>' \
-d '{
  "search": {
    "filter": {
      "$and": [
        { "purchasedDate": { "$gte": "2026-10-01T00:00:00.000Z" } },
        { "purchasedDate": { "$lt": "2026-11-01T00:00:00.000Z" } }
      ]
    },
    "sort": [{ "fieldName": "purchasedDate", "order": "ASC" }],
    "cursorPaging": { "limit": 100 }
  }
}'

Unpaid orders of one buyer that contain a product:

curl -X POST 'https://www.wixapis.com/ecom/v1/orders/search' \
-H 'Content-Type: application/json' \
-H 'Authorization: <AUTH>' \
-d '{
  "search": {
    "filter": {
      "buyerInfo.email": "jane@example.com",
      "paymentStatus": "NOT_PAID",
      "status": { "$in": ["APPROVED", "PENDING"] },
      "lineItems.productName.original": { "$hasSome": ["Baseball Cap"] }
    }
  }
}'

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.

{ "search": { "cursorPaging": { "limit": 100, "cursor": "<metadata.cursors.next>" } } }

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

Field What it holds
id Order ID, for Get Order and for dashboard links
number The order number the owner sees
purchasedDate When the order was placed
status APPROVED, CANCELED, PENDING, REJECTED, or INITIALIZED (only from Get Order)
paymentStatus PAID, NOT_PAID, PARTIALLY_PAID, PENDING, PARTIALLY_REFUNDED, FULLY_REFUNDED, and others
fulfillmentStatus NOT_FULFILLED, PARTIALLY_FULFILLED, FULFILLED
currency Currency of every amount in the order
priceSummary.total.amount Order total, as a decimal string ("414.00"); also subtotal, shipping, tax, discount
lineItems[].productName.original Item name
lineItems[].quantity Units of the item
lineItems[].totalPriceAfterTax.amount What the buyer paid for that line
lineItems[].catalogReference.catalogItemId Product ID of the item
buyerInfo.email, buyerInfo.contactId The buyer
billingInfo.contactDetails firstName, lastName, phone, company
billingInfo.address city, country, postalCode, addressLine
recipientInfo Who receives the order; shippingInfo.logistics.shippingDestination holds the shipping address, or the pickup address for pickup orders

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:

curl -X POST 'https://www.wixapis.com/ecom/v1/payments/list-by-ids' \
-H 'Content-Type: application/json' \
-H 'Authorization: <AUTH>' \
-d '{ "orderIds": ["<order id>", "<order id>"] }'

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.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 alert1d4 checks · Risk SAFE
  • Gen Agent Trust Hub1d

    The skill is a comprehensive management tool for Wix sites. It contains potential security risks such as an indirect prompt injection surface from site scraping and the ability to define JavaScript-based automation logic, but it includes strong requirements for user confirmation before any site changes.

  • Socket2d

    No alerts

  • Snyk1d

    Risk: CRITICAL · 3 issues

  • ZeroLeaks7mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at e2bc48e. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 4 days ago
compatibility
Requires Wix REST API access (API key or OAuth).
  • wix
  • rest-api
  • ecommerce
  • bookings
  • cms
  • contacts
  • blog
  • domains
  • restaurants
  • site-configuration
  • api-integration

README badge

README badge for wix/skills/wix-manage

REST API operations for configuring Wix business solutions including stores, bookings, CMS, contacts, domains, and ecommerce. Routes to site setup, entity management (products, services, staff), bulk administrative operations, and server-to-server integrations across Wix's business app ecosystem.

Generated from the current SKILL.md.

Do I need API credentials to use these recipes?
Yes. The skill requires Wix REST API access via either an API key or OAuth token to execute any management operations.
Can I use these recipes to display data on my site frontend?
No. These recipes are for backend REST API operations only — site configuration, entity management, and administrative tasks. They do not cover frontend development or displaying data to users.
What business domains do these recipes cover?
The skill covers stores, bookings, payments, CMS, contacts, forms, media, apps, pricing plans, restaurants, rich content, sites, blogs, calendars, domains, and site properties.
Do these recipes handle OAuth authentication with external services like Google Calendar?
Yes. The external calendar integration recipe covers OAuth-based setup with Google Calendar, Microsoft Outlook, and Apple Calendar for bidirectional event sync.

Generated from the current SKILL.md. These answers refresh after source changes.