@wix/agent-skills 1.0.0

package/skills/wix-manage/references/get-paid/how-to-setup-wix-payments.md

@@ -0,0 +1,57 @@
+---
+name: "How to Setup Wix Payments"
+description: Configures Wix Payments as the payment provider. Covers eligibility checking, business verification, bank account setup, and payment method configuration (cards, PayPal, Apple Pay).
+---
+# 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://www.wix.com/about/terms-of-payments
+2. First name
+3. Last name
+4. Product/service description (minimum meaningful business description)
+
+## Step 2: Connect Wix Payments account
+
+Call:
+
+- `POST https://www.wixapis.com/payments/v1/wix-payments-account/connect`
+
+```json
+{
+  "account": {
+    "firstName": "<USER_FIRST_NAME>",
+    "lastName": "<USER_LAST_NAME>",
+    "tosAccepted": true,
+    "productDescription": "<PRODUCT_DESCRIPTION>"
+  }
+}
+```
+
+## Step 3: 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](https://dev.wix.com/docs/api-reference/business-management/locations/update-location)
+
+### Already connected
+
+If the API returns an "already connected" style response, skip reconnect and continue with onboarding checks.
+
+## Step 4: 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.
+
+## Important Notes
+
+1. Never invent or assume user identity/business details.
+2. Always obtain explicit user consent before calling connect.
+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.

package/skills/wix-manage/references/get-paid/payment-links-for-bookings.md

@@ -0,0 +1,101 @@
+---
+name: "Payment Links for Bookings"
+description: Creates payment links for unpaid bookings using Payment Links API. Links booking IDs to payment requests with proper redirect handling.
+---
+# Payment Links for Bookings
+
+Use this recipe to collect payment for booking-related flows by generating payment links with the Payment Links API.
+
+## When to Use Which Type
+
+### Use `ECOM_ORDER` for existing unpaid orders
+
+If a booking already has an associated unpaid eCommerce order, create an `ECOM_ORDER` payment link.
+
+```json
+{
+  "paymentLink": {
+    "title": "Booking Balance",
+    "currency": "USD",
+    "type": "ECOM_ORDER",
+    "paymentsLimit": 1,
+    "ecomOrderPaymentLink": {
+      "orderId": "ORDER_ID",
+      "amount": "50"
+    }
+  }
+}
+```
+
+Notes:
+- `orderId` must exist and be unpaid.
+- `ECOM_ORDER` links require `paymentsLimit: 1`.
+
+### Use `ECOM` for ad-hoc booking charges
+
+If there is no existing order, create an `ECOM` payment link with custom line items.
+
+```json
+{
+  "paymentLink": {
+    "title": "Booking Fee",
+    "currency": "USD",
+    "type": "ECOM",
+    "ecomPaymentLink": {
+      "lineItems": [
+        {
+          "type": "CUSTOM",
+          "customItem": {
+            "name": "Booking Fee",
+            "quantity": 1,
+            "price": "50.00"
+          }
+        }
+      ]
+    }
+  }
+}
+```
+
+## Send Flow
+
+Creating a payment link does not deliver it. Send it explicitly:
+
+- `POST https://www.wixapis.com/payment-links/v1/payment-links/{paymentLinkId}/send`
+
+```json
+{
+  "paymentLinkId": "PAYMENT_LINK_ID",
+  "recipients": [
+    {
+      "contactId": "CONTACT_ID",
+      "sendMethods": ["EMAIL_METHOD"]
+    }
+  ]
+}
+```
+
+## Prerequisites
+
+Before creating booking payment links, ensure:
+
+1. Site is premium.
+2. Site is published.
+3. Site is set up to accept payments.
+4. Required payment-link permissions are granted to the app.
+5. Recipient contacts exist if you plan to send links.
+
+## 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 |
+| `ORDER_NOT_FOUND` | The provided order ID does not exist |
+| `INVALID_PAYMENTS_LIMIT_FOR_ECOM_ORDER_PAYMENT_LINK` | `ECOM_ORDER` links require `paymentsLimit: 1` |
+| `RECIPIENT_NOT_FOUND` | Recipient contact ID does not exist |
+
+## API Documentation References
+
+- [Create Payment Link](https://dev.wix.com/docs/api-reference/business-management/get-paid/payment-links/payment-links/create-payment-link)
+- [Send Payment Link](https://dev.wix.com/docs/api-reference/business-management/get-paid/payment-links/payment-links/send-payment-link)

package/skills/wix-manage/references/media/upload-media-to-wix.md

@@ -0,0 +1,216 @@
+---
+name: "Upload Media to Wix"
+description: Uploads images and files to the Wix Media Manager using the Import File API. Covers importing from external URLs, checking file status, and using the returned wixstatic.com URL in other APIs.
+---
+# RECIPE: Upload Media to Wix Media Manager
+
+Learn how to upload images and files to a Wix site's Media Manager using the REST API.
+
+---
+
+## Overview
+
+The Wix Media Manager stores all media files for a site. When you need to use images or files in other Wix APIs, you should first upload them to the Media Manager to get a reliable wixstatic.com URL.
+
+**Key Points:**
+- Uploaded files are permanently stored on Wix servers
+- You get back a `url` (wixstatic.com) that works reliably in other APIs
+- External URLs can fail if the source server blocks requests - Media Manager URLs never fail
+
+---
+
+## Method: Import File from External URL
+
+The simplest way to add media is to import it from an external URL. Wix will download and store the file.
+
+### API Endpoint
+
+```
+POST https://www.wixapis.com/site-media/v1/files/import
+```
+
+### Request Example
+
+```bash
+curl -X POST 'https://www.wixapis.com/site-media/v1/files/import' \
+-H 'Content-Type: application/json' \
+-H 'Authorization: <AUTH>' \
+-d '{
+    "url": "https://images.unsplash.com/photo-1563729784474-d77dbb933a9e?w=400",
+    "mimeType": "image/jpeg",
+    "displayName": "My Image"
+}'
+```
+
+### Request Parameters
+
+| Parameter | Required | Description |
+|-----------|----------|-------------|
+| `url` | Yes | The external URL of the file to import |
+| `mimeType` | Recommended | MIME type (e.g., `image/jpeg`, `image/png`). If omitted, Wix tries to detect it |
+| `displayName` | No | Display name in Media Manager. Include extension (e.g., `My Image.jpg`) |
+| `parentFolderId` | No | Folder ID to store the file. Defaults to `media-root` |
+
+### Response Example
+
+```json
+{
+    "file": {
+        "id": "e6a89e_19dae9fef9bb48a6b5e392d0d2e5b95d~mv2.jpg",
+        "displayName": "My Image.jpg",
+        "url": "https://static.wixstatic.com/media/e6a89e_19dae9fef9bb48a6b5e392d0d2e5b95d~mv2.jpg",
+        "parentFolderId": "media-root",
+        "mediaType": "IMAGE",
+        "operationStatus": "PENDING",
+        "sizeInBytes": "31911"
+    }
+}
+```
+
+### Key Response Fields
+
+| Field | Description |
+|-------|-------------|
+| `id` | Media ID |
+| `url` | **The wixstatic.com URL - use this in other APIs** |
+| `operationStatus` | `PENDING` → `READY` when processed, or `FAILED` if import failed |
+
+> **Can I Use the URL Immediately?**
+>
+> **In most cases, yes.** The returned `wixstatic.com` URL typically works immediately for basic use cases like adding to products or blog posts.
+>
+> **Wait for READY when:**
+> - You need image dimensions or metadata
+> - You're using image transformations (resize, crop)
+> - You want guaranteed consistency for critical operations
+>
+> **Practical approach:** Try using the URL immediately. If it fails, poll until `operationStatus: "READY"`.
+
+---
+
+## Checking File Status
+
+After importing, the file goes through async processing. For guaranteed consistency, verify `operationStatus: "READY"` before using the file.
+
+### Get File by ID (Recommended)
+
+Use this endpoint to check the status of a specific file:
+
+```bash
+curl -X GET 'https://www.wixapis.com/site-media/v1/files/get-file-by-id?fileId={fileId}' \
+-H 'Authorization: <AUTH>'
+```
+
+**Example:**
+
+```bash
+curl -X GET 'https://www.wixapis.com/site-media/v1/files/get-file-by-id?fileId=e6a89e_9d32c0dbae954582bce7b2bf35981ca6~mv2.jpg' \
+-H 'Authorization: <AUTH>'
+```
+
+### List Recent Files (Alternative)
+
+If you need to find files without knowing the ID:
+
+```bash
+curl -X GET 'https://www.wixapis.com/site-media/v1/files?parentFolderId=media-root&mediaTypes=IMAGE&sort.fieldName=updatedDate&sort.order=DESC&paging.limit=5' \
+-H 'Authorization: <AUTH>'
+```
+
+### Status Values
+
+| Status | Meaning |
+|--------|---------|
+| `PENDING` | Still processing - wait before using |
+| `READY` | File is ready to use |
+| `FAILED` | Import failed |
+
+### Response When Ready
+
+```json
+{
+    "files": [{
+        "id": "e6a89e_19dae9fef9bb48a6b5e392d0d2e5b95d~mv2.jpg",
+        "url": "https://static.wixstatic.com/media/e6a89e_19dae9fef9bb48a6b5e392d0d2e5b95d~mv2.jpg",
+        "operationStatus": "READY",
+        "media": {
+            "image": {
+                "image": {
+                    "height": 600,
+                    "width": 400
+                }
+            }
+        },
+        "labels": ["cupcakes", "pastry", "dessert"]
+    }]
+}
+```
+
+> **Note:** Wix automatically generates labels (tags) for images using AI.
+
+---
+
+## Alternative: Upload from Local Device
+
+If you need to upload files from a local device (not from a URL), use the two-step upload process:
+
+### Step 1: Generate Upload URL
+
+```bash
+curl -X POST 'https://www.wixapis.com/site-media/v1/files/generate-upload-url' \
+-H 'Content-Type: application/json' \
+-H 'Authorization: <AUTH>' \
+-d '{
+    "mimeType": "image/jpeg",
+    "fileName": "my-photo.jpg"
+}'
+```
+
+### Step 2: Upload to the Generated URL
+
+```bash
+curl -X PUT '<UPLOAD_URL_FROM_RESPONSE>' \
+-H 'Content-Type: image/jpeg' \
+--data-binary @my-photo.jpg
+```
+
+> **Note:** For files larger than 10MB, use the Resumable Upload URL API instead.
+
+---
+
+## Common Issues
+
+### Issue 1: Import Fails (operationStatus: FAILED)
+
+**Problem:** The file shows `operationStatus: "FAILED"` after import.
+
+**Causes:**
+- Source server blocks external requests (e.g., Wikipedia, some CDNs)
+- Source server requires authentication
+- Invalid URL or file not found
+- File type not supported
+
+**Solution:** Use image sources that allow hotlinking:
+- Unsplash (`images.unsplash.com`)
+- Pexels (`images.pexels.com`)
+- Your own hosted images
+- Public cloud storage (S3, GCS with public access)
+
+### Issue 2: File Stuck in PENDING
+
+**Problem:** File stays in `PENDING` status for a long time.
+
+**Solution:**
+- Large files take longer to process
+- Check back after a few seconds
+- If still pending after 30+ seconds, the import may have silently failed
+
+---
+
+## Summary
+
+| Step | Action | Result |
+|------|--------|--------|
+| 1 | Call Import File API with external URL | Get file `id` and `url` with status `PENDING` |
+| 2 | Poll List Files API | Wait for `operationStatus: "READY"` |
+| 3 | Use in other APIs | Use the `url` field (wixstatic.com URL) |

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

@@ -0,0 +1,77 @@
+---
+name: "Create and Update Pricing Plans"
+description: Creates subscription and one-time payment plans using Plans API. Covers pricing models (recurring, one-time, free), trial periods, perks configuration, and plan visibility.
+---
+# Technical Step-by-Step Instructions: Creating or Updating a Wix Pricing Plans (Real-World, API-First)
+
+## Description
+Below are the recommended steps to successfully create or update a Wix Pricing Plans (or several at once) on Wix and attach a booking session to a pricing plan, with real-world troubleshooting and fixes for common API issues.
+
+---
+
+## Overview
+Wix Pricing Plans includes Plans that allows Wix users to build a customized membership plan experiences and sell them to their customers. Pricing plans can also have bundled booking session as benefits.
+
+- With Plans, a site owner can create different types of plans, such as, free, one-time or recurring subscriptions and memberships.
+- With Benefits, a site owner can connect other wix apps like booking service to a pricing plan subscription or membership. Read the full list of pricing plan integration [here](https://dev.wix.com/docs/api-reference/business-solutions/pricing-plans/introduction#integrations).
+
+### IMPORTANT NOTES
+- Always Prioritize Reading Full API Method Documentation: this overview article provides a general workflow. However, it repeatedly stresses the importance of reading the full documentation for each specific REST method you intend to use. This is critical for understanding detailed requirements.
+- Pay close attention to all required fields, data types, enum values, and specific ID types (e.g., resourceId vs. id) as defined in the detailed schema of each API endpoint. The overview article serves as a guide but doesn't replace the need to consult these specifics.
+
+---
+
+## Steps
+### 0. Read pricing plans API docs
+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.
+
+### 2. Attach integrating app entity to pricing plans
+
+To attach integrating app entity, like bookings or blog to pricing plans read the [Benefit Programs](https://dev.wix.com/docs/api-reference/business-solutions/benefit-programs/introduction) documentation and proceed to further steps.
+
+#### 2.1. Find program definition
+
+Use [Get Program Definition By External Id And Namespace](https://dev.wix.com/docs/api-reference/business-solutions/benefit-programs/program-definitions/get-program-definition-by-external-id-and-namespace) endpoint to find the corresponding program definition of the plan. The call must have these query params:
+- `externalId` must be equal to pricing plan id.
+- `namespace` must be `@wix/pricing-plans`
+
+Example the request in curl:
+```bash
+curl --request GET \
+  "https://www.wixapis.com/benefit-programs/v1/program-definitions/by-namespace-and-external-id?externalId=00000000-0000-0000-0000-000000000001&namespace=@wix/pricing-plans" \
+  -H 'Authorization: <AUTH>' \
+  -H "Content-Type: application/json"
+```
+
+#### 2.2. Create a pool definition
+
+Only one pool definition per integrating app must be created. The pool definition should be created using [create pool definition](https://dev.wix.com/docs/api-reference/business-solutions/benefit-programs/pool-definitions/create-pool-definition) endpoint.
+
+The request for this endpoint must adhere to these rules:
+- `namespace` must be `@wix/pricing-plans`
+-  only one benefit can be defined in the pool definition
+- benefit benefitKey must be a random generated UUID
+- benefit provider app id must be the integrating app def id. For the full list of wix app def ids read [this](https://dev.wix.com/docs/api-reference/articles/get-started/apps-created-by-wix) article.
+- benefit price must be only 1 or 0. 0 - if you want the benefit to have unlimited credits and 1 - for the benefit to be limited.
+- `creditConfiguration` must be empty if the benefit is unlimited
+
+#### 2.3. Create benefit items
+
+This step is needed to attach the integrating app entity to benefit program. This is done by using [bulk create items](https://dev.wix.com/docs/api-reference/business-solutions/benefit-programs/items/bulk-create-items) endpoint.
+
+Each item in the request for this endpoint must adhere to these rules:
+- `namespace` must be `@wix/pricing-plans`
+-  `category` must be empty string
+- provider app id must be the integrating app def id. For the full list of wix app def ids read [this](https://dev.wix.com/docs/api-reference/articles/get-started/apps-created-by-wix) article.
+- `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.
+
+## 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)
+- [Update plan](https://dev.wix.com/docs/api-reference/business-solutions/pricing-plans/plans-v3/update-plan)
+- [Query Plans](https://dev.wix.com/docs/api-reference/business-solutions/pricing-plans/plans-v3/query-plans)
+- [Pricing Plans Introduction](https://dev.wix.com/docs/api-reference/business-solutions/pricing-plans/introduction)

package/skills/wix-manage/references/pricing-plans/pricing-plans-bookings-integration.md

@@ -0,0 +1,166 @@
+---
+name: "Pricing Plans Bookings Integration"
+description: Links Pricing Plans to Bookings services using the Benefit Programs API. Enables package deals and memberships that grant booking access.
+---
+
+# Technical Step-by-Step Instructions: Integrating Wix Pricing Plans with Bookings Services (Real-World, API-First)
+
+## Description
+
+Below are the recommended steps to successfully integrate Wix Pricing Plans with Wix Bookings services, enabling customers to purchase packages and memberships for booking sessions. This recipe covers the complete workflow including the required Benefit Programs integration.
+
+---
+
+## Prerequisites
+
+### Required App Installations
+
+Before starting the integration, ensure the following apps are installed on the site:
+
+1. **Wix Bookings** - Usually pre-installed, but verify using site queries
+2. **Pricing Plans** - Must be installed if not present
+   - Install if you encounter 428 "App not installed" errors
+
+### App Installation Process
+
+If you receive app-related errors, install the missing app using the Apps Installer API.
+
+**Steps:**
+
+1. Identify the required app through error messages or API documentation
+2. Use the Apps Installer API to install the missing app
+3. Verify installation before proceeding
+
+**For detailed app installation procedures, refer to:**
+
+- [Apps Installer API Documentation](https://dev.wix.com/docs/api-reference/business-management/app-installation/install-app)
+- Business setup recipes for app installation workflows
+- API error messages which typically indicate the required app and installation steps
+
+## Overview
+
+Integrating Pricing Plans with Bookings allows businesses to offer:
+
+- **Packages**: Fixed session count (e.g., "10 sessions") that can be used within validity period
+- **Memberships with session limits**: Sessions per billing cycle (e.g., "10 sessions a month")
+- **Unlimited memberships**: Unlimited access during subscription period (shows as "Unlimited Sessions")
+
+The integration requires coordination between three APIs:
+
+1. **Pricing Plans API** - Creates the plan structure and pricing
+2. **Benefit Programs API** - Creates the bridge between plans and services
+3. **Bookings API** - Services automatically support pricing plan payments
+
+### IMPORTANT NOTES
+
+- The integration requires using all three APIs in sequence - there's no direct connection between Pricing Plans and Bookings
+- This is a complex integration that requires careful error handling and state management
+- Service `payment.options.pricingPlan` automatically becomes `true` when benefit programs are properly connected
+- The benefit program `externalId` must exactly match the pricing plan `id` for the connection to work
+- **Minimum Duration Requirements**: Plans must have minimum 7-day validity periods - cannot create 1-day plans
+- **Revision Number Management**: The Benefit Programs API uses revision numbers that can conflict with concurrent operations
+
+---
+
+## Steps
+
+### 1. Create the Pricing Plan
+
+Create the pricing plan first using the Pricing Plans API. You can create either:
+
+- **Package plans** using `singlePaymentForDuration` pricing model with `"type": "bookings-package"` in `clientData`
+- **Membership plans** using `subscription` pricing model with `"type": "bookings-membership"` in `clientData`
+
+**Important Validation Requirements:**
+
+- `validity.duration` must be minimum 7 days (`P7D` format)
+- Cannot use `P1D` or shorter periods due to API validation
+- For subscription plans, billing cycles have similar minimum requirements
+
+Keep the returned `plan.id` for the next step.
+
+### 2. Create Benefit Program Definition
+
+Use the Benefit Programs API to create the program definition that links to your pricing plan. The `externalId` must exactly match the pricing plan `id` from step 1, and use `"@wix/pricing-plans"` as the namespace.
+
+**Error Handling Note**: If you receive "Entity already exists" errors, the program definition may already exist from a previous attempt. Query existing programs first or handle the error gracefully.
+
+### 3. Create Benefit Definition for Bookings Service
+
+Create the benefit definition that connects the program to your specific booking service:
+
+- For **packages with session limits**: Include `creditAmount` set to the desired session count
+- For **unlimited memberships**: Omit the `creditAmount` field entirely
+- Always use the correct `serviceId` from your bookings service and `"@wix/pricing-plans"` namespace
+
+**Revision Number Handling**: The Benefit Programs API requires revision numbers. If operations fail due to revision conflicts, retrieve the current revision number and retry.
+
+### 4. Verify Service Integration
+
+Query the service to confirm integration is working. The service should now show `payment.options.pricingPlan: true` and the plan should appear in the booking UI as a payment option.
+
+### IMPORTANT NOTES
+
+- **Sequence matters**: Create pricing plan → benefit program definition → benefit definition. Wrong order will cause "Plan not found" errors
+- **Complex State Management**: This integration involves multiple APIs with different revision systems and error handling patterns
+- **ID relationships**:
+  - Pricing Plan `id` → Benefit Program Definition `externalId`
+  - Service `id` → Benefit Definition `serviceId`
+  - Program Definition `id` → Benefit Definition `programDefinitionId`
+- **Session behavior**:
+  - With `creditAmount`: Users consume credits per session
+  - Without `creditAmount`: Users get unlimited access during subscription
+- **Namespace requirement**: Always use `"@wix/pricing-plans"` as namespace for pricing plan integrations
+- **Service updates**: Services automatically update when benefit programs are connected - no manual service modification needed
+
+### Troubleshooting Common Issues
+
+**"App not installed" Error (428):**
+
+- Install Pricing Plans app using Apps Installer API
+- Verify installation before proceeding with plan creation
+
+**"Plan not found" Error:**
+
+- Verify `externalId` exactly matches pricing plan `id`
+- Ensure pricing plan was created successfully before creating benefit program
+- Check that the plan hasn't been deleted or modified
+
+**"Entity already exists" Error:**
+
+- Query existing benefit program definitions to check for duplicates
+- Consider updating existing programs instead of creating new ones
+- Implement proper error handling for idempotent operations
+
+**Service doesn't show pricing plan option:**
+
+- Check that benefit definition has correct `serviceId`
+- Verify all three entities (plan, program definition, benefit definition) were created successfully
+- Confirm service query shows `payment.options.pricingPlan: true`
+
+**Credits not working correctly:**
+
+- For packages: Ensure `creditAmount` is set to desired session count
+- For unlimited: Ensure `creditAmount` is omitted entirely
+- Verify the benefit definition is properly linked to the correct program definition
+
+**Minimum Duration Validation Errors:**
+
+- Ensure `validity.duration` is at least `P7D` (7 days)
+- Adjust single-session plans to weekly validity instead of daily
+- For subscription plans, use appropriate billing cycle minimums
+
+**Revision Number Conflicts:**
+
+- Implement retry logic with fresh revision number retrieval
+- Handle concurrent operations gracefully
+- Consider queuing operations if dealing with high-frequency updates
+
+## API Documentation References
+
+- [Create Plan](https://dev.wix.com/docs/api-reference/business-solutions/pricing-plans/plans-v3/create-plan) — `POST https://www.wixapis.com/pricing-plans/v3/plans`
+- [Create Program Definition](https://dev.wix.com/docs/api-reference/business-solutions/benefit-programs/program-definitions/create-program-definition) — `POST https://www.wixapis.com/_api/benefit-programs/v1/program-definitions`
+- [Pricing Plans API](https://dev.wix.com/docs/api-reference/business-solutions/pricing-plans/introduction)
+- [Benefit Programs API](https://dev.wix.com/docs/api-reference/business-solutions/benefit-programs/introduction)
+- [Bookings Services API](https://dev.wix.com/docs/api-reference/business-solutions/bookings/services/introduction)
+- [Apps Installer API](https://dev.wix.com/docs/api-reference/business-management/app-installation/install-app)