> To build or manage a Wix site with an AI agent, follow https://www.wix.com/headless/skill.md
> It builds a new Wix site or puts your own site online, from a prompt, and keeps changing it afterwards. The pages are code in any web technology, and Wix runs the backend.
> It works through the Wix plugin (the Wix MCP and the Wix skills), the Wix CLI or no Wix login, and puts the site live on Wix hosting or on another host.
> Business features include a store, bookings, events and tickets, a restaurant, a blog, forms, members and many more.
> Read the Wix skills online at https://www.wix.com/skills
> 
> Portal Navigation:
> 
> - Append `.md` to any URL under `https://dev.wix.com/docs/` to get its markdown version.
> - Pages are either content pages (article or reference text) or menu pages (a list of links to child pages).
> - To get a menu page, truncate any URL to a parent path and append `.md` (e.g. `https://dev.wix.com/docs/sdk.md`, `https://dev.wix.com/docs/sdk/core-modules.md`).
> - If a reference page seems to be missing its schema (parameters, return types, or type definitions), append `?schema=true` to its `.md` URL (e.g. `https://dev.wix.com/docs/contexts/contexts/stores/category-info/use-category-info-context.md?schema=true`).
> - Top-level index of all portals: https://dev.wix.com/docs/llms.txt
> - Full concatenated docs: https://dev.wix.com/docs/llms-full.txt

# listFormsProvidersConfigs

# Package: @wix/forms

# Namespace: forms

# Method link: https://dev.wix.com/docs/api-reference/crm/forms/form-schemas/list-forms-providers-configs.md

## Permission Scopes:
Manage forms: SCOPE.FORMS.EDIT-FORM

## Introduction

Retrieves a list of the form schema provider configurations available on a site.

Each configuration is what a provider app, such as Wix Forms or Wix Bookings, declares in the app dashboard for a namespace it owns. The response covers the provider apps installed on a site, plus apps made by Wix that Wix includes without installation.

Use the response to discover which namespaces a site can create form schemas in. Don't use it to predict whether Create Form succeeds, because a provider declares these values once for all sites, while Wix validates form schema creation against the state of an individual site:

+ The response omits `restrictions` when a provider declares none. Default platform limits still apply, so a missing `restrictions` doesn't mean unlimited.
+ Create Form and Update Form enforce limits this response doesn't carry, such as a maximum serialized form schema size.
+ A provider that enables schema validation validates every create and update itself, and can reject a form schema based on a site's own state. For example, the Wix Forms app derives its form, field, step, condition, and email recipient limits, along with the availability of premium-only field types such as file upload and payment fields, from a site's premium plan. A create can fail for that reason even when the request respects the values returned here.

For the limits in force for a site, call Get Restrictions, which returns the site's plan-derived caps along with its current form count. To find out whether a form schema is valid for a site, call Create Form or Update Form and read the validation errors it returns.

---

## JavaScript SDK

### Schema

```
 Method: wixClientAdmin.forms.forms.listFormsProvidersConfigs()
 Description: Retrieves a list of the form schema provider configurations available on a site.  Each configuration is what a provider app, such as Wix Forms or Wix Bookings, declares in the app dashboard for a namespace it owns. The response covers the provider apps installed on a site, plus apps made by Wix that Wix includes without installation.  Use the response to discover which namespaces a site can create form schemas in. Don't use it to predict whether Create Form succeeds, because a provider declares these values once for all sites, while Wix validates form schema creation against the state of an individual site:  + The response omits `restrictions` when a provider declares none. Default platform limits still apply, so a missing `restrictions` doesn't mean unlimited. + Create Form and Update Form enforce limits this response doesn't carry, such as a maximum serialized form schema size. + A provider that enables schema validation validates every create and update itself, and can reject a form schema based on a site's own state. For example, the Wix Forms app derives its form, field, step, condition, and email recipient limits, along with the availability of premium-only field types such as file upload and payment fields, from a site's premium plan. A create can fail for that reason even when the request respects the values returned here.  For the limits in force for a site, call Get Restrictions, which returns the site's plan-derived caps along with its current form count. To find out whether a form schema is valid for a site, call Create Form or Update Form and read the validation errors it returns.
 Return type: PROMISE<ListFormsProvidersConfigsResponse>
  - name: configs | type: array<FormsSchemaProvidersConfig> | description: List of configurations set by form schema providers.  | validation: maxItems 50
     - name: namespace | type: string | description: Namespace of the app which provides this configuration  | validation: maxLength 50
     - name: appId | type: string | description: GUID of app which provides this config.  | validation: maxLength 36
     - name: restrictions | type: FormProviderRestrictions | description: Restrictions on form schemas declared by this app for this namespace.  The response omits this field when the app declares no restrictions, in which case default platform limits apply. These are the app's declared values, not the limits in force for a site.  
        - name: maxForms | type: integer | description: Maximum number of forms allowed per namespace on a site. Doesn't include deleted forms.  | validation: minimum 0, maximum 15000
        - name: maxFields | type: integer | description: Maximum number of input fields allowed per form. Display elements, such as rich content and the submit button, don't count toward this limit.  | validation: minimum 0, maximum 200
        - name: maxDeletedForms | type: integer | description: Maximum number of deleted forms allowed per namespace on a site. Forms in the trash bin count toward this limit.  | validation: minimum 1000, maximum 1000, format int32


```

### Examples

### listFormsProvidersConfigs
```javascript
import { forms } from '@wix/forms';

async function listFormsProvidersConfigs() {
  const response = await forms.listFormsProvidersConfigs();
};
```

### listFormsProvidersConfigs (with elevated permissions)
```javascript
import { forms } from '@wix/forms';
import { auth } from '@wix/essentials';

async function myListFormsProvidersConfigsMethod() {
  const elevatedListFormsProvidersConfigs = auth.elevate(forms.listFormsProvidersConfigs);
  const response = await elevatedListFormsProvidersConfigs();
}
```

### listFormsProvidersConfigs (self-managed)
Self-managed SDK calls require you to [create a client](https://dev.wix.com/docs/sdk/articles/work-with-the-sdk/about-the-wix-client.md).

```javascript
import { createClient } from '@wix/sdk';
import { forms } from '@wix/forms';
// Import the auth strategy for the relevant access type
// Import the relevant host module if needed

const myWixClient = createClient ({
  modules: { forms },
  // Include the auth strategy and host as relevant
});


async function listFormsProvidersConfigs() {
  const response = await myWixClient.forms.listFormsProvidersConfigs();
};
```

---