@wix/agent-skills 1.15.1 → 1.16.0

package/skills/wix-manage/references/google-ads/query-campaign-analytics.md

@@ -0,0 +1,155 @@
+---
+name: "Query Campaign Performance Analytics"
+description: "Reads performance analytics for a Google Ads campaign on a Wix site: daily performance metrics (impressions, clicks, CTR, cost, leads, phone calls) with optional previous-period comparison and trends; conversion metrics from Wix Analytics (orders, revenue, leads, CPL, ROAS); the search terms that triggered a campaign's ads; per-product shopping performance for retail campaigns; and per-asset performance (headlines, descriptions, images) for PMAX Leads. Explains when to use campaignResourceName vs the Wix campaignId, the dateRange shape, field enums, sorting, and paging. Use when the user asks 'how is my campaign doing', 'show ad performance', 'what search terms triggered my ads', 'which products/assets perform best', 'campaign ROI/ROAS', or 'conversions from my Google ads'. REST base https://www.wixapis.com/google-ads/v1."
+---
+# RECIPE: Query Campaign Performance Analytics
+
+Read how a Google Ads campaign is performing. Six query endpoints cover different breakdowns; picking the right one depends on the metric and the campaign type. Performance data is only available once a campaign is `LIVE`, and typically appears within a few hours of activity.
+
+Base URL: `https://www.wixapis.com/google-ads/v1` (search-term V2 is under `/v2`). `<AUTH>` is the `Authorization` header; body calls also need `Content-Type: application/json`. All endpoints are read-only.
+
+**Two identifiers — get them right:**
+- **`campaignResourceName`** — the Google Ads resource name `customers/{customerId}/campaigns/{campaignId}` (from `campaign.resourceName`). Used by **Performance Metrics** and **Search Term Metrics (v1)**.
+- **`campaignId`** — the Wix-internal campaign GUID (from `campaign.id`). Used by **Conversion Metrics**, **Shopping Performance**, **Asset Performance**, and **Search Term Metrics V2**.
+
+Both come from Get/List Campaign (see [Manage Campaign Lifecycle](manage-campaign-lifecycle.md)).
+
+**Which query?**
+
+| Question | Endpoint | Campaign types | ID |
+| --- | --- | --- | --- |
+| Daily impressions/clicks/CTR/cost/leads | `POST /v1/performance-metrics` | all | `campaignResourceName` |
+| Orders / revenue / ROAS (from Wix) | `POST /v1/conversion-metrics` | all | `campaignId` |
+| Which search queries triggered ads | `POST /v2/search-term-metrics` | Smart + PMAX Leads | `campaignId` |
+| Per-product performance | `POST /v1/shopping-performance-metrics` | Shopping / retail PMAX | `campaignId` |
+| Per-asset (headline/description/image) | `POST /v1/asset-performance-metrics` | PMAX Leads only | `campaignId` |
+
+**Date range** is shared: `{ "dateRange": { "custom": { "from": "2026-03-01", "to": "2026-03-31" } } }` (YYYY-MM-DD). Omit `dateRange` to default to the campaign lifetime.
+
+---
+
+## Daily performance metrics
+
+Clicks, impressions, CTR, cost, leads, phone calls — per day, plus a summary row. `fields` chooses which metrics to return (defaults to clicks, impressions, CTR, cost, phone calls, date). `includePreviousPeriod: true` adds a `previousPeriodSummaryRow` and `trends` (decimal % change vs the equivalent preceding period).
+
+```bash
+curl -X POST 'https://www.wixapis.com/google-ads/v1/performance-metrics' \
+  -H 'Authorization: <AUTH>' -H 'Content-Type: application/json' \
+  -d '{
+    "campaignResourceName": "customers/3827461950/campaigns/7412836509",
+    "dateRange": { "custom": { "from": "2026-03-01", "to": "2026-03-31" } },
+    "fields": ["DATE", "IMPRESSIONS", "CLICKS", "CTR", "COST", "LEADS"],
+    "sort": { "field": "DATE", "order": "DESC" },
+    "includePreviousPeriod": true
+  }'
+```
+
+```json
+{
+  "results": [ { "date": "2026-03-31", "impressions": 1820, "clicks": 128, "ctr": 0.0703, "cost": 54.20, "leads": 3 } ],
+  "summaryRow": { "impressions": 47381, "clicks": 3316, "ctr": 0.0699, "cost": 1408.65, "leads": 87 },
+  "previousPeriodSummaryRow": { "impressions": 41020, "clicks": 2874, "ctr": 0.0700, "cost": 1215.40, "leads": 71 },
+  "trends": { "impressions": 0.155, "clicks": 0.154, "ctr": -0.001, "cost": 0.159, "leads": 0.225 }
+}
+```
+
+`fields` enum: `DATE`, `IMPRESSIONS`, `CLICKS`, `CTR`, `COST`, `LEADS`, `PHONE_CALLS`, `COST_PER_CLICK`, `CLICKS_BY_AD_NETWORK_TYPE`, `IMPRESSIONS_BY_AD_NETWORK_TYPE`. `ctr` and `trends` are decimals (`0.0703` = 7.03%; `0.155` = +15.5%). `cost` is already in currency units (converted from micros).
+
+## Conversion metrics (orders, revenue, ROAS)
+
+Business outcomes from **Wix Analytics** (not Google). Both `campaignId` and `dateRange` are **required**. Complex query — 120s SLA.
+
+```bash
+curl -X POST 'https://www.wixapis.com/google-ads/v1/conversion-metrics' \
+  -H 'Authorization: <AUTH>' -H 'Content-Type: application/json' \
+  -d '{ "campaignId": "b3f8e241-7c4a-4d19-a562-9f1e30d87c05", "dateRange": { "custom": { "from": "2026-03-01", "to": "2026-03-31" } } }'
+```
+
+```json
+{ "summaryRow": { "orders": 214, "revenue": 18750.40, "leads": 87, "cpl": 16.19, "leadsConversionRate": 0.0262, "cpp": 6.58, "roas": 13.31 } }
+```
+
+## Search terms that triggered ads
+
+The actual queries users typed. Use **V2** (`/v2/search-term-metrics`, keyed by `campaignId`) — it supports both Smart and PMAX Leads. Optional `searchTermText` (contains-match) and `searchTermTextsFilter` (`{ type: "MATCH" | "NOT_MATCH", searchTermTexts: [...] }`). Sortable by `COST`/`CLICKS`/`IMPRESSIONS`; paged with `nextPageToken`.
+
+```bash
+curl -X POST 'https://www.wixapis.com/google-ads/v2/search-term-metrics' \
+  -H 'Authorization: <AUTH>' -H 'Content-Type: application/json' \
+  -d '{
+    "campaignId": "b3f8e241-7c4a-4d19-a562-9f1e30d87c05",
+    "searchTermText": "leather bag",
+    "dateRange": { "custom": { "from": "2026-03-01", "to": "2026-03-31" } },
+    "sort": { "field": "CLICKS", "order": "DESC" },
+    "paging": { "pageSize": 10 }
+  }'
+```
+
+```json
+{
+  "results": [ { "searchTerm": "leather bag women", "impressions": 5632, "clicks": 421, "cost": 176.82 } ],
+  "summaryRow": { "searchTerm": "", "impressions": 9522, "clicks": 719, "cost": 301.98 },
+  "nextPageToken": "CAoQAA"
+}
+```
+
+(The v1 `/v1/search-term-metrics` variant exists but takes `campaignResourceName` and is Smart-only — prefer V2.)
+
+## Per-product shopping performance (retail / Shopping PMAX)
+
+Product-level rows for a Shopping campaign, plus a summary with total conversions, revenue, and ROAS. `resultSetting` controls the payload: `SUMMARY_ONLY`, `RESULTS_ONLY`, or `SUMMARY_AND_RESULTS`. 120s SLA. Note: per-product `conversions`/`conversionRate` always return 0 (not queried from Google) — use the summary's `totalConversions`/`roas` for outcomes.
+
+```bash
+curl -X POST 'https://www.wixapis.com/google-ads/v1/shopping-performance-metrics' \
+  -H 'Authorization: <AUTH>' -H 'Content-Type: application/json' \
+  -d '{
+    "campaignId": "b3f8e241-7c4a-4d19-a562-9f1e30d87c05",
+    "dateRange": { "custom": { "from": "2026-03-01", "to": "2026-03-31" } },
+    "fields": ["IMPRESSIONS", "CLICKS", "CTR", "COST", "COST_PER_CLICK"],
+    "sort": { "field": "COST", "order": "DESC" },
+    "paging": { "pageSize": 10 },
+    "resultSetting": "SUMMARY_AND_RESULTS"
+  }'
+```
+
+Results carry `productTitle`, `productImageUrl`, and the Wix `productId`; the `summaryRow` has `totalConversions`, `totalRevenue`, `roas`, and `moreResultsAvailable`.
+
+## Per-asset performance (PMAX Leads only)
+
+Which creative assets perform best. `filter.assetTypes` narrows to specific roles (`HEADLINE`, `DESCRIPTION`, `MARKETING_IMAGE`, …).
+
+```bash
+curl -X POST 'https://www.wixapis.com/google-ads/v1/asset-performance-metrics' \
+  -H 'Authorization: <AUTH>' -H 'Content-Type: application/json' \
+  -d '{
+    "campaignId": "b3f8e241-7c4a-4d19-a562-9f1e30d87c05",
+    "dateRange": { "custom": { "from": "2026-03-01", "to": "2026-03-31" } },
+    "fields": ["IMPRESSIONS", "CLICKS", "CTR", "COST", "ASSET_SOURCE"],
+    "sort": { "field": "IMPRESSIONS", "order": "DESC" },
+    "filter": { "assetTypes": ["HEADLINE", "DESCRIPTION", "MARKETING_IMAGE"] }
+  }'
+```
+
+Each result has `assetContent`, `assetFieldType`, `assetSource` (`ADVERTISER` vs auto-generated), a `performanceLabel` (`EXCELLENT`/`GOOD`/…), and a nested `metrics` object.
+
+---
+
+## Error handling
+
+| Symptom | Cause | Fix |
+| --- | --- | --- |
+| Empty results / all-zero metrics | Campaign not `LIVE`, or no activity yet in the range | Confirm the campaign is live; data lags a few hours. Widen the date range |
+| `ACCOUNT_NOT_FOUND` / `CAMPAIGN_NOT_FOUND` | Wrong id or no account | Verify via List/Get Campaign |
+| Wrong-id error on performance/search-term-v1 | Passed `campaignId` where `campaignResourceName` is required (or vice-versa) | Match the ID column in the "Which query?" table |
+| Asset-performance returns nothing on a non-Leads campaign | Only PMAX Leads is supported | Use performance/shopping metrics for other types |
+| Shopping per-product `conversions`/`conversionRate` are 0 | By design (not queried from Google) | Read the summary's `totalConversions`/`roas` |
+| Slow response (conversion/shopping) | 120s SLA | Wait; don't retry prematurely |
+
+## References
+
+- [Analytics Service introduction](https://dev.wix.com/docs/api-reference/business-management/marketing/ads/google-ads/performance-metrics-v1/introduction)
+- [Query Performance Metrics](https://dev.wix.com/docs/api-reference/business-management/marketing/ads/google-ads/performance-metrics-v1/query-performance-metrics)
+- [Query Conversion Metrics](https://dev.wix.com/docs/api-reference/business-management/marketing/ads/google-ads/performance-metrics-v1/query-conversion-metrics)
+- [Query Search Term Metrics V2](https://dev.wix.com/docs/api-reference/business-management/marketing/ads/google-ads/performance-metrics-v1/query-search-term-metrics-v2)
+- [Query Shopping Performance Metrics](https://dev.wix.com/docs/api-reference/business-management/marketing/ads/google-ads/performance-metrics-v1/query-shopping-performance-metrics)
+- [Query Asset Performance Metrics](https://dev.wix.com/docs/api-reference/business-management/marketing/ads/google-ads/performance-metrics-v1/query-asset-performance-metrics)

package/skills/wix-manage/references/marketing/marketing-dashboard-navigation.md

@@ -0,0 +1,52 @@
+---
+name: "Marketing Dashboard Navigation"
+description: "Builds direct links to Wix marketing dashboard pages on manage.wix.com — the social posts hub (drafts, scheduled and published posts across connected channels), post design templates, saved designs, and the email marketing pages (campaigns list, campaign templates, campaign analytics). Pairs each main marketing entity (social post item, connected social account, marketing-plan post, email campaign) with its read API so you can fetch an entity and hand back a 'view it in your dashboard' link. Use when the user asks where something is in the Wix dashboard, wants a direct link to a dashboard page, or you need a dashboard URL to include with the result of an API operation."
+---
+
+# Marketing Dashboard Navigation
+
+Build direct links into the marketing pages of a site's dashboard. For the general URL contract (metaSiteId, fallbacks, redirects), see [Dashboard Navigation](../dashboard-navigation/dashboard-navigation.md).
+
+Marketing pages are split across **two apps** with two URL namespaces:
+
+- **Social Media Marketing** (`f27ff649-0249-4a0c-9438-841cbbfd2514`) — social posts, design templates. Routes under `social-marketing-web/`.
+- **Email Marketing** (`135c3d92-0fea-1f9d-2ba5-2a1dfb04297e`) — email campaigns. Routes under `email-marketing/`.
+
+Older links (`social-marketing`, `social-marketing/my-posts`, `shoutout`) redirect to the current routes.
+
+## Social Posts Pages (Social Media Marketing)
+
+| Page | URL after `/dashboard/{metaSiteId}/` | What it manages |
+|---|---|---|
+| Social posts hub | `social-marketing-web` | Draft, scheduled, and published social posts across connected channels; create a new post |
+| Design templates | `social-marketing-web/design-templates` | Post design template gallery |
+| My designs | `social-marketing-web/my-designs` | Saved post designs |
+
+Posts created or scheduled via the Publisher API (see [Create and Publish a Social Media Post](./create-and-publish-social-post.md)) and posts generated from an AI marketing plan (see [Generate a Marketing Plan](./generate-and-publish-marketing-plan.md)) all appear on the social posts hub.
+
+## Email Marketing Pages (Email Marketing)
+
+| Page | URL after `/dashboard/{metaSiteId}/` | What it manages |
+|---|---|---|
+| Email marketing home | `email-marketing` | Email marketing hub |
+| My campaigns | `email-marketing/my-campaigns` | All email campaigns (sent, scheduled, drafts) |
+| Campaign templates | `email-marketing/template-list` | Start a campaign from a template |
+| Campaign analytics | `email-marketing/analytics` | Campaign statistics |
+
+## Pairing Entities with Their Read APIs
+
+Fetch the entity via REST, then link the matching dashboard page. All calls use `https://www.wixapis.com` with an `Authorization` header.
+
+| Entity | Read API | Dashboard link |
+|---|---|---|
+| Social post (item) | Publisher API Item — created via `POST /social-publisher/v1/items`, published/scheduled via `POST /social-publisher/v1/publish-by-id` | `social-marketing-web` |
+| Connected social account | `GET /social-publisher/v1/accounts?channelName={CHANNEL}` | `social-marketing-web` |
+| Marketing-plan post | `GET /promote/marketing-plan-service/v1/marketing-plan?timeframe.startDate=...&timeframe.endDate=...` · `POST /promote/marketing-plan-service/v1/marketing-activity-posts` | `social-marketing-web` (scheduled posts land on the hub) |
+| Email campaign | `GET /email-marketing/v1/campaigns` · `GET /email-marketing/v1/campaigns/{campaignId}` | `email-marketing/my-campaigns` |
+
+Example — after scheduling a social post, hand back the hub link:
+
+```
+Scheduled your Instagram post for tomorrow 9:00.
+See it here: https://manage.wix.com/dashboard/{metaSiteId}/social-marketing-web
+```

package/skills/wix-manage/references/pricing-plans/create-and-update-pricing-plans.md

@@ -26,7 +26,87 @@ Wix Pricing Plans includes Plans that allows Wix users to build a customized mem
 Before proceeding to further steps I must read the following [documentation](https://dev.wix.com/docs/api-reference/business-solutions/pricing-plans/introduction) on how to form request to pricing plans API.
 
 ### 1. Create a pricing plan
-Creating a pricing plan can be done by using [create plan](https://dev.wix.com/docs/api-reference/business-solutions/pricing-plans/plans-v3/create-plan) endpoint.
+Create plans with the [Create Plan](https://dev.wix.com/docs/api-reference/business-solutions/pricing-plans/plans-v3/create-plan) endpoint: `POST https://www.wixapis.com/pricing-plans/v3/plans`.
+
+Prerequisites: the site must have the Wix Pricing Plans app installed, and a site currency must be
+set — Create Plan returns `404 CURRENCY_MISSING` when the currency isn't set in site settings.
+
+#### Required request fields
+
+Send all of these on every create request. Two of them are easy to miss, so check them before
+sending:
+
+| Field | Notes |
+| --- | --- |
+| `plan.status` | Set to `"ACTIVE"`. **The generated Create Plan method schema does not list this field, but the server requires it.** Omitting it returns `400` with `plan.status: value is required` (`REQUIRED_FIELD`). The code examples on the Create Plan article all include it. |
+| `plan.visibility` | `"PUBLIC"` or `"PRIVATE"`. |
+| `plan.pricingVariants[].id` | **You must generate this GUID yourself — it is not server-assigned.** This is unusual for a create call, and it's the most common cause of a failed first attempt. Omitting it returns `400` with `plan.pricingVariants[0].id: is not a valid GUID` and `must not be empty`. Generate a fresh UUID per variant. |
+| `plan.pricingVariants[].name` | Variant name, e.g. `"Monthly"` or the plan name for a single-variant plan. |
+| `plan.pricingVariants[].billingTerms.startType` | `"ON_PURCHASE"` or `"CUSTOM"`. |
+| `plan.pricingVariants[].billingTerms.endType` | `"UNTIL_CANCELLED"` or `"CYCLES_COMPLETED"`. With `CYCLES_COMPLETED`, also send `billingTerms.cyclesCompletedDetails.billingCycleCount`. |
+| `plan.pricingVariants[].pricingStrategies[]` | Exactly one strategy. Use `flatRate.amount` as a decimal **string**, e.g. `"0"` or `"5.99"`. |
+
+`pricingVariants` is currently limited to one variant per plan.
+
+#### Minimal free plan
+
+This is the complete minimal body for a free plan — copy it and change the names and the variant
+GUID:
+
+```javascript
+async function() {
+  return await wix.request({
+    method: 'POST',
+    url: 'https://www.wixapis.com/pricing-plans/v3/plans',
+    body: {
+      plan: {
+        name: 'Free Tier',
+        visibility: 'PUBLIC',
+        status: 'ACTIVE',
+        buyable: true,
+        buyerCanCancel: true,
+        pricingVariants: [
+          {
+            id: '7a3f1e2d-4b5c-6d7e-8f9a-0b1c2d3e4f5a', // generate a fresh GUID
+            name: 'Free Tier',
+            pricingStrategies: [{ flatRate: { amount: '0' } }],
+            billingTerms: {
+              startType: 'ON_PURCHASE',
+              endType: 'UNTIL_CANCELLED'
+            }
+          }
+        ]
+      }
+    }
+  });
+}
+```
+
+Do **not** add a `billingCycle` to a free plan: a free plan can't be recurring, and the server
+rejects that combination with `400 FREE_PRICING_VARIANT_IS_NOT_RECURRING`.
+
+#### Other plan types
+
+Same required fields; only `billingTerms` and the `flatRate.amount` change.
+
+| Plan type | `billingTerms` |
+| --- | --- |
+| Free, open-ended | Omit `billingCycle`; `endType: "UNTIL_CANCELLED"`. `flatRate.amount: "0"`. |
+| One-time payment, fixed duration | `billingCycle` = the duration (e.g. `{ period: 'MONTH', count: 1 }`), `endType: "CYCLES_COMPLETED"`, `cyclesCompletedDetails.billingCycleCount: 1`. |
+| Recurring, until cancelled | `billingCycle` = the recurrence (e.g. `{ period: 'MONTH', count: 1 }`), `endType: "UNTIL_CANCELLED"`. |
+
+A `billingCycle` can't be shorter than 7 days, and total plan duration can't exceed 10 years
+(`400 VALID_BILLING_CYCLE` / `400 VALID_PLAN_DURATION`).
+
+Two more optional fields worth knowing:
+
+- **Purchase caps.** In V3 these are `plan.purchaseLimits`, an array of
+  `{ type, maxCount }`. `type` is one of `PER_MEMBER_LIFETIME`, `PER_MEMBER_ACTIVE`,
+  `TOTAL_ACTIVE`, `TOTAL_SOLD`. To make a plan available only once per member, send
+  `purchaseLimits: [{ type: 'PER_MEMBER_LIFETIME', maxCount: 1 }]`. Some Create Plan examples still
+  use the V2-era `maxPurchasesPerBuyer` field; `purchaseLimits` is the V3 equivalent.
+- **Free trials.** `pricingVariants[].freeTrialDays` only applies to recurring *paid* plans — using
+  it on a free plan returns `400 FREE_TRIAL_IS_APPLICABLE`.
 
 ### 2. Attach integrating app entity to pricing plans
 
@@ -69,6 +149,24 @@ Each item in the request for this endpoint must adhere to these rules:
 - `itemSetId` must set to the created pool definition benefit item set id.
 - `externalId` must be set to the integrating app entity id, example: booking service id or blog post id.
 
+### 3. Stop offering a plan — archive it, don't delete it
+
+When the user asks to archive, retire, or stop offering a plan, **archive** it so existing
+subscribers and order history are preserved. Archiving is an Update Plan call — there is no
+separate archive endpoint, and Delete Plan is not the same thing:
+
+```bash
+curl -X PATCH \
+  'https://www.wixapis.com/pricing-plans/v3/plans/<PLAN_ID>' \
+  -H 'Authorization: <AUTH>' \
+  -H 'Content-Type: application/json' \
+  -d '{ "plan": { "id": "<PLAN_ID>", "revision": "<CURRENT_REVISION>", "archived": true } }'
+```
+
+Carry the plan's current `revision` or the update is rejected. `archived` is not listed in the
+generated Plan object reference, so it cannot be found by reading the schema — reach for it
+directly rather than searching for an archive method or falling back to Delete Plan.
+
 ## Pricing plans REST API Documentation Reference
 - [Create plan](https://dev.wix.com/docs/api-reference/business-solutions/pricing-plans/plans-v3/create-plan)
 - [Get plan](https://dev.wix.com/docs/api-reference/business-solutions/pricing-plans/plans-v3/get-plan)

package/skills/wix-manage/references/pricing-plans/pricing-plans-dashboard-navigation.md

@@ -0,0 +1,45 @@
+---
+name: "Pricing Plans Dashboard Navigation"
+description: "Builds direct links to Wix Pricing Plans dashboard pages on manage.wix.com — plans list, create a plan, edit a plan, record a manual order, and settings. Pairs each main Pricing Plans entity (plan, order) with its read API so you can fetch an entity and hand back a 'view it in your dashboard' link. Use when the user asks where something is in the Wix dashboard, wants a direct link to a dashboard page, or you need a dashboard URL to include with the result of an API operation."
+---
+
+# Pricing Plans Dashboard Navigation
+
+Build direct links into the Wix Pricing Plans pages of a site's dashboard. For the general URL contract (metaSiteId, fallbacks, redirects), see [Dashboard Navigation](../dashboard-navigation/dashboard-navigation.md).
+
+All Wix Pricing Plans (app ID `1522827f-c56c-a5c9-2ac9-00f9e6ae12d3`) pages live under:
+
+```
+https://manage.wix.com/dashboard/{metaSiteId}/pricing-plans/{route}
+```
+
+## Main Pages
+
+| Page | URL after `/dashboard/{metaSiteId}/` | What it manages |
+|---|---|---|
+| Plans list | `pricing-plans` | All pricing plans; purchases (orders/subscriptions) are a tab of this page |
+| Create plan | `pricing-plans/new` | New plan form |
+| Edit plan | `pricing-plans/edit` | A specific plan — reached from the plans list (no documented ID path segment) |
+| New manual order | `pricing-plans/new-order` | Record a manual (offline) plan order for a member |
+| Settings | `pricing-plans/settings` | Pricing Plans settings |
+
+There is no separate route for the purchases list — it is a tab of the main `pricing-plans` page.
+
+Older `membership...` links (`membership`, `paid-plans`, `membership/setup`, `membership/orders/new`, `membership-settings`) redirect to the current routes.
+
+## Pairing Entities with Their Read APIs
+
+Fetch the entity via REST, then link the matching dashboard page. All calls use `https://www.wixapis.com` with an `Authorization` header.
+
+| Entity | Read API | Dashboard link |
+|---|---|---|
+| Plan | `POST /pricing-plans/v3/plans/query` · `GET /pricing-plans/v3/plans/{planId}` | `pricing-plans` (list) or `pricing-plans/edit` (opened from the list) |
+| Order (subscription/purchase) | `GET /pricing-plans/v2/orders` · `GET /pricing-plans/v2/orders/{id}` | `pricing-plans` (purchases tab) |
+| Settings | Pricing Plans Settings API (Get Pricing Plans Settings) | `pricing-plans/settings` |
+
+Example — after creating a plan, hand back the plans page:
+
+```
+Created "Gold Membership".
+Manage it here: https://manage.wix.com/dashboard/{metaSiteId}/pricing-plans
+```

package/skills/wix-manage/references/restaurants/restaurants-dashboard-navigation.md

@@ -0,0 +1,68 @@
+---
+name: "Restaurants Dashboard Navigation"
+description: "Builds direct links to Wix Restaurants dashboard pages on manage.wix.com — menus, menu items, the online orders board, online-ordering fulfillment settings (pickup, delivery, dine-in), the reservations list, floor plans, and reservation experience settings. Pairs each main Restaurants entity (menu, section, item, order, reservation) with its read API so you can fetch an entity and hand back a 'view it in your dashboard' link. Use when the user asks where something is in the Wix dashboard, wants a direct link to a dashboard page, or you need a dashboard URL to include with the result of an API operation."
+---
+
+# Restaurants Dashboard Navigation
+
+Build direct links into the restaurant pages of a site's dashboard. For the general URL contract (metaSiteId, fallbacks, redirects), see [Dashboard Navigation](../dashboard-navigation/dashboard-navigation.md).
+
+Restaurant pages are split across **three apps** with three URL namespaces:
+
+- **Wix Restaurants Menus** (`b278a256-2757-4f19-9313-c05c783bec92`) — menus, sections, items. Routes under `wix-restaurants-menus-new/`.
+- **Wix Restaurants Orders** (`9a5d83fd-8570-482e-81ab-cfa88942ee60`) — online orders board and online-ordering settings. Routes under `wix-restaurants-orders-new/`.
+- **Wix Table Reservations** (`f9c07de2-5341-40c6-b096-8eb39de391fb`) — reservations, floor plans, reservation experiences. Routes under `wix-table-reservations/`.
+
+Older links (`restaurants/menus-management`, `restaurants/table-reservations`, `restaurants-orders-prep-board`, `olo-settings/...`) redirect to the current routes.
+
+## Menus Pages (Wix Restaurants Menus)
+
+| Page | URL after `/dashboard/{metaSiteId}/` | What it manages |
+|---|---|---|
+| Menus | `wix-restaurants-menus-new` | All menus (and their sections) |
+| Edit menu | `wix-restaurants-menus-new/menu/{menuId}` | A specific menu |
+| Items | `wix-restaurants-menus-new/items` | All menu items |
+| Menu printing | `wix-restaurants-menus-new/menus-printing` | Print-ready menu export |
+
+## Orders Pages (Wix Restaurants Orders)
+
+| Page | URL after `/dashboard/{metaSiteId}/` | What it manages |
+|---|---|---|
+| Orders board | `wix-restaurants-orders-new` | Incoming online orders (prep board) |
+| Online orders settings | `wix-restaurants-orders-new/settings` | Online-ordering settings hub |
+
+Fulfillment and ordering sub-settings live at `wix-restaurants-orders-new/settings/{subpage}`: `pickup`, `delivery`, `pickup-delivery`, `dine-in`, `closure-dates`, `scheduling-page`, `service-fee`, `printing`, `doordash`.
+
+## Reservations Pages (Wix Table Reservations)
+
+| Page | URL after `/dashboard/{metaSiteId}/` | What it manages |
+|---|---|---|
+| Reservations list | `wix-table-reservations/table-reservations` | All table reservations |
+| Floor plan view | `wix-table-reservations/floor-plan-view` | Live floor-plan view of reservations |
+| Floor plan editor | `wix-table-reservations/floor-plan` | Table layout (floor plan) |
+| Create experience | `wix-table-reservations/create-experience` | New reservation experience |
+| Experience settings | `wix-table-reservations/experience` | A reservation experience (seating rules, policies) |
+
+Experience sub-settings live at `wix-table-reservations/experience/{subpage}`: `details`, `schedule`, `reservation-form`, `reservation-settings`, `table-assignment`, `polices`.
+
+## Pairing Entities with Their Read APIs
+
+Fetch the entity via REST, then link the matching dashboard page. All calls use `https://www.wixapis.com` with an `Authorization` header.
+
+| Entity | Read API | Dashboard link |
+|---|---|---|
+| Menu | `POST /restaurants/menus-menu/v1/menus/query` · `GET /restaurants/menus-menu/v1/menus` | `wix-restaurants-menus-new/menu/{menuId}` (edit) or `wix-restaurants-menus-new` (list) |
+| Section | `POST /restaurants/menus-section/v1/sections/query` | `wix-restaurants-menus-new` (sections are managed inside their menu) |
+| Item | `POST /restaurants/menus-item/v1/items/query` | `wix-restaurants-menus-new/items` |
+| Order | `POST /ecom/v1/orders/search` · `GET /ecom/v1/orders/{orderId}` | `wix-restaurants-orders-new` (board) or `ecom-platform/order-details/{orderId}` |
+| Reservation | `POST /table-reservations/reservations/v1/reservations/query` · `GET /table-reservations/reservations/v1/reservations/{reservationId}` | `wix-table-reservations/table-reservations` |
+| Reservation location (settings) | `POST /table-reservations/reservation-locations/v1/reservation-locations/query` | `wix-table-reservations/experience` |
+
+Restaurant online orders are eCommerce orders (their `lineItems[].catalogReference.appId` is `9a5d83fd-8570-482e-81ab-cfa88942ee60`), so they can also be read and linked through the eCommerce orders pages.
+
+Example — after creating a menu, hand back its edit link:
+
+```
+Created "Dinner Menu".
+Manage it here: https://manage.wix.com/dashboard/{metaSiteId}/wix-restaurants-menus-new/menu/{menuId}
+```