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.

referencesgoogle-adsbilling-and-payment.md

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

RECIPE: Retrieve Google Ads Billing and Payment Details

Report what a site owner will be charged for Google Ads: ad spend, the Wix service fee, coupon adjustments, the total, the billing period, and the account's credit balance.

Base URL: https://www.wixapis.com/_serverless/pa-google/v1. <AUTH> is the Authorization header. This endpoint is read-only.

Prerequisite: a Google Ads account must exist (ACCOUNT_NOT_FOUND → run install-and-create-account).


Get payment details

Billing is calculated from cached subscription data (not fetched live from Google), and the charge calculation is heavy — this endpoint has a 30-second SLA, so allow time and don't retry prematurely.

curl -X GET 'https://www.wixapis.com/_serverless/pa-google/v1/payment-details' -H 'Authorization: <AUTH>'
{
  "paymentDetails": {
    "currency": "USD",
    "upcomingPayments": [
      {
        "usageAmount": "123.45",
        "wixServiceFee": "12.35",
        "totalAmount": "135.80",
        "billingPeriod": { "from": "2026-03-01", "to": "2026-03-31" },
        "couponAdjustmentAmount": "0.00"
      }
    ],
    "creditBalance": "0.00"
  }
}

Reading the response:

  • currency — the account's billing currency; all amounts here are in it.
  • upcomingPayments[] — the current billing period breakdown (up to 2 entries). Per entry:
    • usageAmount — ad spend for the period, excluding the Wix fee.
    • wixServiceFee — the Wix platform fee.
    • couponAdjustmentAmount — discount applied from a promotional coupon.
    • totalAmount — what will actually be charged: usageAmount + wixServiceFee − couponAdjustmentAmount.
    • billingPeriod — from/to dates (YYYY-MM-DD).
  • creditBalance — the site's credits. Positive = credits available (e.g. from an incentive) that offset upcoming charges; negative = outstanding debt not yet charged. The final amount can shift slightly once the charge is processed.

When summarizing for the user, lead with totalAmount and the billing period, then break out spend vs fee, and flag a non-zero creditBalance (credits remaining, or debt owed).

Note: an older monthlyPayments field is deprecated in favor of upcomingPayments — always read upcomingPayments.


Budget vs. billing — a related but different view

Payment details cover charges. The account object (from GET /v1/accounts/current-site, see install-and-create-account) carries the ad-budget view:

  • currentBudget — remaining ad budget/credit (negative = debt not yet charged).
  • spentBudget — total spent on ads so far.

Use payment details for "what will I be charged and when"; use the account's budget fields for "how much ad budget is left."


Error handling

Symptom Cause Fix
NOT_FOUND / ACCOUNT_NOT_FOUND No Google Ads account for the site Run install-and-create-account
Slow response (up to ~30s) Charge calculation SLA Wait; don't retry prematurely
upcomingPayments empty No charges accrued yet this period Report zero upcoming charges; check creditBalance for credits/debt
Negative creditBalance Outstanding debt not yet charged Explain it's owed and will be charged; not an error

References

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.