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-paidhow-to-setup-wix-payments.md

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

How to Set Up Wix Payments

This recipe covers the setup flow needed before creating payment links or collecting payments.

Step 1: Collect required user inputs

Before connecting Wix Payments, collect and confirm:

  1. Terms acceptance: https://support.wix.com/en/article/wix-payments-terms-of-service
  2. First name
  3. Last name
  4. Product/service description (minimum meaningful business description)
  5. The site's country — if not already known, get it from properties.locale.country via GET https://www.wixapis.com/site-properties/v4/properties

Step 2: Check country support

Wix Payments self-serve connect is currently supported for these countries: US, CA, GB, ES, AT, BE, FI, DE, IT, NL, PT, CH, LT.

If the site's country is not on this list, stop here — do not call connect. Tell the user self-serve connect isn't available yet for their country, and point them to the dashboard instead (Settings → Accept Payments).

Step 3: Connect Wix Payments account

Call:

  • POST https://www.wixapis.com/payments/v1/wix-payments-account/connect
{
  "account": {
    "firstName": "<USER_FIRST_NAME>",
    "lastName": "<USER_LAST_NAME>",
    "tosAccepted": true,
    "productDescription": "<PRODUCT_DESCRIPTION>",
    "country": "<COUNTRY_CODE verified in Step 2>"
  }
}

Step 4: Handle common setup blockers

Location-related failure

If setup fails due to location details, update the business location and retry:

  • PUT https://www.wixapis.com/locations/v1/locations/{locationId}
  • Reference: Update Location

Already connected

If the account is already connected, the API returns HTTP 500 with a body like:

{
  "message": "payments already connected",
  "details": { "applicationError": { "code": "INTERNAL_ERROR" } }
}

Match on the message text, not on the code alone — INTERNAL_ERROR is a generic code reused for unrelated failures too. On this match, skip reconnect and continue with onboarding checks.

Unsupported country

If account.country isn't one of the countries listed in Step 2, expect an INVALID_ARGUMENT-style HTTP 400 error. Step 2's own check should make hitting this rare — don't retry the call with a different country value; tell the user the same thing Step 2 would have.

Step 5: Complete dashboard onboarding

Connecting the account is not always the final step. To receive payments, the site owner may still need to complete Wix Payments onboarding in the site dashboard.

Connecting Wix Payments and being able to accept real checkout payments are two separate gates: the site may also need a premium eCommerce plan (Settings → Plans). Mention this even after a successful connect.

Important Notes

  1. Never invent or assume user identity/business details.
  2. Always obtain explicit user consent before calling connect — this creates a real Wix Payments account and records a legally-binding Terms of Service acceptance under the name provided.
  3. Use the exact accepted values provided by the user.
  4. Verify readiness by testing a real payment flow (for example, create payment link) after setup.

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.