All skills
wix avatar

/wix-manage

@4895cc9 official
by Wix.comwix/skills33 stars
33

REST recipes to configure and manage a Wix site's business solutions — stores, bookings, payments, CMS, and more. 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: stores, bookings, get-paid, CMS, contacts, forms, media, app-installation, pricing-plans, restaurants, ricos rich-content, sites, blog, calendar, domains, events, site-properties, ecommerce, marketing, google-ads, google-business-profile, analytics, accessibility, seo, dashboard-navigation.

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

This session only. Nothing lands on disk.

referencesget-paidcreate-payment-links.md

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

Create Payment Links

This recipe shows how to create and manage payment links using the current Payment Links REST API.

Prerequisites

  1. Site is premium.
  2. Site is published.
  3. Site is set up to accept payments (Wix Payments onboarding completed).
  4. App has payment-link permissions.
  5. Wix Stores is installed if you plan to charge for catalog products.

Required APIs

  • Payment Links API: REST
  • Products API: REST

Overview

Payment links are created at:

  • POST https://www.wixapis.com/payment-links/v1/payment-links

Use one of these payment-link types:

  • ECOM: charge for custom or catalog line items.
  • ECOM_ORDER: collect payment for an existing unpaid eCommerce order.

Step 1: Retrieve product details (optional)

If you plan to use catalog items, fetch the product first.

Examples:

  • Catalog V1: GET https://www.wixapis.com/stores/v1/products/{productId}
  • Catalog V1 query: POST https://www.wixapis.com/stores/v1/products/query
{
  "query": {
    "paging": {
      "limit": 50,
      "offset": 0
    }
  }
}

Step 2: Create an ECOM payment link with custom line items

{
  "paymentLink": {
    "title": "Business Listing Fee",
    "description": "One-time listing fee",
    "currency": "USD",
    "type": "ECOM",
    "ecomPaymentLink": {
      "lineItems": [
        {
          "type": "CUSTOM",
          "customItem": {
            "name": "Listing Fee",
            "quantity": 1,
            "price": "200.00"
          }
        }
      ]
    }
  }
}

Step 3: Create an ECOM payment link with catalog items

{
  "paymentLink": {
    "title": "Product Payment",
    "currency": "USD",
    "type": "ECOM",
    "ecomPaymentLink": {
      "lineItems": [
        {
          "type": "CATALOG",
          "catalogItem": {
            "quantity": 1,
            "catalogReference": {
              "appId": "215238eb-22a5-4c36-9e7b-e7c08025e04e",
              "catalogItemId": "PRODUCT_ID",
              "options": {
                "variantId": "VARIANT_ID"
              }
            }
          }
        }
      ]
    }
  }
}

Step 4: Create an ECOM_ORDER payment link for an existing order

{
  "paymentLink": {
    "title": "Order Balance",
    "currency": "USD",
    "type": "ECOM_ORDER",
    "paymentsLimit": 1,
    "ecomOrderPaymentLink": {
      "orderId": "ORDER_ID",
      "amount": "50"
    }
  }
}

Step 5: Send payment link to recipients

Use:

  • POST https://www.wixapis.com/payment-links/v1/payment-links/{paymentLinkId}/send

Request body:

{
  "paymentLinkId": "PAYMENT_LINK_ID",
  "recipients": [
    {
      "contactId": "CONTACT_ID",
      "sendMethods": ["EMAIL_METHOD"]
    }
  ]
}

Step 6: Query and manage payment links

Query:

  • POST https://www.wixapis.com/payment-links/v1/payment-links/query
{
  "query": {
    "filter": {
      "status": "ACTIVE"
    },
    "cursorPaging": {
      "limit": 50
    }
  }
}

Get one:

  • GET https://www.wixapis.com/payment-links/v1/payment-links/{paymentLinkId}

Deactivate:

  • POST https://www.wixapis.com/payment-links/v1/payment-links/{paymentLinkId}/deactivate

Activate:

  • POST https://www.wixapis.com/payment-links/v1/payment-links/{paymentLinkId}/activate

Delete (only when no payments were received):

  • DELETE https://www.wixapis.com/payment-links/v1/payment-links/{paymentLinkId}

Payment Link Statuses

Status Description
ACTIVE Link is active and can receive payments
INACTIVE Link is inactive and cannot receive payments
PAID Payment has been completed
EXPIRED Link has passed its expiration date

Common Errors

Error Code Meaning
UNPUBLISHED_SITE Site must be published before creating payment links
MISSING_ACCEPT_PAYMENTS Site is not set up to accept payments
FAILED_TO_INSTALL_ECOM Required eCommerce capability is missing
RECIPIENT_NOT_FOUND Provided recipient contact does not exist
ORDER_NOT_FOUND Provided order ID does not exist
INVALID_PAYMENTS_LIMIT_FOR_ECOM_ORDER_PAYMENT_LINK ECOM_ORDER links require paymentsLimit: 1

Best Practices

  1. Validate prerequisites first (premium, published, payments enabled).
  2. Use ECOM for line-item collection and ECOM_ORDER for existing unpaid orders.
  3. Use IDs from real entities (products, variants, contacts, orders).
  4. Keep currency aligned with your business/order currency rules.
  5. Persist payment-link IDs and monitor status via query/get methods.

Related Documentation

Source: SKILL.md on GitHub

1 warning1d4 checks · Risk SAFE
  • Gen Agent Trust Hub1d

    The wix-manage skill is an extensive collection of management recipes for Wix sites, covering business solutions such as eCommerce, Bookings, SEO, and site provisioning. It utilizes official Wix REST endpoints and incorporates robust safety patterns, including mandatory user confirmation for sensitive operations and careful validation of site data before mutation.

  • Socket1d

    No alerts

  • Snyk1d

    Risk: MEDIUM · 1 issue

  • ZeroLeaks5mo

    Score: 93/100 · 2 sections analyzed

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

Last checked against GitHub yesterday.

Activeupdated yesterday
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.