# About the Data Extension Schema API

A data extension schema allows you to define and validate the structure of additional custom fields that can be dynamically added to Wix API objects. This schema acts as a blueprint, describing the properties, data types, and constraints for these custom `extendedFields` fields, based on a [JSON schema](fallback::https://dev.wix.com/docs/build-apps/develop-your-app/extensions/backend-extensions/schema-plugins/the-json-schema) as part of the [schema plugin extension](fallback::https://dev.wix.com/docs/build-apps/develop-your-app/extensions/backend-extensions/schema-plugins/about-schema-plugin-extensions). For example, a data extension schema can describe custom shipping data added to the [Wix eCommerce Checkout object](fallback::https://dev.wix.com/docs/sdk/backend-modules/ecom/checkout/get-checkout).

The Data Extension Schema API enables you to: 
- [Retrieve all the data extension schemas](fallback::https://dev.wix.com/docs/sdk/backend-modules/data-extension-schemas/schemas/list-data-extension-schemas) installed on a site.
- [Create](fallback::https://dev.wix.com/docs/sdk/backend-modules/data-extension-schemas/schemas/create-data-extension-schema) and [update](fallback::https://dev.wix.com/docs/sdk/backend-modules/data-extension-schemas/schemas/update-data-extension-schema) user-defined schemas for a site.

Learn more about [reading and writing schema plugin fields](fallback::https://dev.wix.com/docs/build-apps/develop-your-app/extensions/backend-extensions/schema-plugins/about-reading-and-writing-schema-plugin-fields).

### User-defined data extension schemas
A user-defined data extension schema is created when a Wix user creates their own extended fields. This schema is saved under a dedicated `_user_fields` `namespace`. For example, Wix users can add their own fields to the checkout flow in the site's dashboard under **Settings** > **Checkout** > **Checkout form** when they edit the checkout form: 

![Checkout extended fields](https://wixmp-833713b177cebf373f611808.wixmp.com/images/eff5a2b4063b0b0b648c2b6f149a6949.png)  

The resulting user-defined data extension is saved in the `_user_fields` `namespace`.

## Before you begin
It's important to note the following before starting to code:
- App schema plugin extensions, including their JSON schemas, are created and maintained in an [app dashboard](fallback::https://manage.wix.com/studio/custom-apps). This API only supports creating and updating **user-defined** schemas.
- Schema plugin extensions are supported by select [Wix API objects](fallback::https://dev.wix.com/docs/build-apps/develop-your-app/extensions/backend-extensions/schema-plugins/about-schema-plugin-extensions#see-also). Always check that the object you would like to extend includes a property named `extendedFields`.
- This API supports retrieving data extension schemas from [multiple `namespaces`](fallback::https://dev.wix.com/docs/build-apps/develop-your-app/extensions/backend-extensions/schema-plugins/about-reading-and-writing-schema-plugin-fields#namespaces) in a single call.
- Data extension schemas are supported by select [Wix API service entities](fallback::https://dev.wix.com/docs/build-apps/develop-your-app/extensions/backend-extensions/schema-plugins/about-schema-plugin-extensions#see-also). Always check that the service object you would like to extend supports this functionality.
- `namespace` name limitations:
  - Can't include "Wix".
  - Only supports lowercase letters, numbers, hyphens, and underscores.
  - Max length: 164 characters.
  - Once set, `namespace` names can't be changed.

## Use cases
- [Retrieve a list of all data extension schemas for the Wix eCommerce Checkout object](fallback::https://dev.wix.com/docs/sdk/backend-modules/data-extension-schemas/schemas/sample-flows#retrieve-a-list-of-all-data-extension-schemas-for-the-Wix-ecommerce-checkout-object)
- [Add fields to a user-defined data extension schema](fallback::https://dev.wix.com/docs/sdk/backend-modules/data-extension-schemas/schemas/sample-flows#add-fields-to-a-user-defined-data-extension-schema-for-the-wix-ecommerce-order-object)
  
## Terminology
- **Data extension schema**: A JSON schema defining the data structure of the custom fields to add to a Wix object. 
- **FQDN**: Fully qualified domain name, a unique identifier for a Wix object. Learn more about [FQDNs](fallback::https://dev.wix.com/docs/rest/articles/get-started/fqdns).
- **Namespace**: A unique identifier for your app or project. Expected format is @myCompany/myAppName. See limitations in the Before you begin section above.
- **Schema plugin extension**: Specific functionality that extends a Wix object with custom fields, nested in the object called `extendedFields`.
- **User-defined schema**: The schema created when a Wix user creates their own extended fields. This schema is created with the `namespace`: `_user_fields`.

@package_metadata:@wix/data-extension-schema

To use the Schemas API, install the `@wix/data-extension-schema` package.

#### Install the package

Follow the installation instructions for your development environment.

| Development environment | Installation method |
|--|--|
| Wix sites (editor or IDE) | Use the [package manager](fallback::https://dev.wix.com/docs/develop-websites/articles/coding-with-velo/packages/work-with-npm-packages-in-the-editor). |
| Wix sites (local IDE) | Run `wix install @wix/data-extension-schema` using the [Wix CLI](fallback::https://dev.wix.com/docs/develop-websites/articles/coding-with-velo/packages/work-with-npm-packages-with-the-wix-cli).|
| Blocks apps | Use the same installation method as Wix sites. |
| CLI and self-hosted apps | Run `npm install @wix/data-extension-schema` or `yarn add @wix/data-extension-schema`. |
| Headless sites and apps | Run `npm install @wix/data-extension-schema` or `yarn add @wix/data-extension-schema`. |

#### Import the package

To import the package in your code:

```js
import { schemas } from '@wix/data-extension-schema'
```

# Sample Flows

This article shares some possible use cases you could support, as well as an example flow that could support each use case. 
You're certainly not limited to these use cases, but they can be a helpful jumping off point as you plan your implementation.

## Retrieve a list of all data extension schemas for the Wix eCommerce Checkout object 
If your functionality requires access to fields that have been added to an object, you might want to retrieve all of the schemas at once. For example, displaying the returned fields to site visitors. 

1. Collect the FQDN of the relevant Wix API service object that [supports schema plugin extensions](fallback::https://dev.wix.com/docs/build-apps/develop-your-app/extensions/backend-extensions/schema-plugins/about-schema-plugin-extensions#see-also). FQDNs are also returned as `entityFqdn` in most events. The Wix eCommerce Checkout FQDN is `wix.ecom.v1.checkout`.
2. Choose the namespaces you would like to retrieve this data for. You can pass multiple namespaces in one call, or leave it blank to retrieve all available namespaces.
3. Call [List Data Extension Schemas](fallback::https://dev.wix.com/docs/sdk/backend-modules/data-extension-schemas/schemas/list-data-extension-schemas) with the FQDN and namespace data.
4. Display the returned data as relevant.

## Add a field to a user-defined data extension schema for the Wix eCommerce Order object
Display a site-specific field, such as alcohol by volume (ABV) for whiskey orders, alongside fields from Wix eCommerce Orders, to site visitors.

1.  Collect the FQDN of the relevant Wix API service object that [supports schema plugin extensions](fallback::https://dev.wix.com/docs/build-apps/develop-your-app/extensions/backend-extensions/schema-plugins/about-schema-plugin-extensions#see-also). FQDNs are also returned as `entityFqdn` in most events. The Wix eCommerce Order FQDN is `wix.ecom.v1.order`.
1. Call [List Data Extension Schemas](fallback::https://dev.wix.com/docs/sdk/backend-modules/data-extension-schemas/schemas/list-data-extension-schemas) with the `wix.ecom.v1.order` FQDN and `_user_fields` namespace to check if a user-defined schema exists.
1. Create or update the `_user_fields` namespace, as relevant:
    1. If no `_user_fields` namespace schema exists, call [Create Data Extension Schema](fallback::https://dev.wix.com/docs/sdk/backend-modules/data-extension-schemas/schemas/create-data-extension-schema) with the `wix.ecom.v1.order` FQDN, the `_user_fields` namespace and the new JSON schema.
    1. If a `_user_fields` namespace schema already exists, call [Update Data Extension Schema](fallback::https://dev.wix.com/docs/sdk/backend-modules/data-extension-schemas/schemas/update-data-extension-schema) with the `wix.ecom.v1.order` FQDN, the `_user_fields` namespace and the updated JSON schema.
1. Display the user-defined field as relevant.

> **Note**: Once you have added at least one user-defined field, you should call [List Data Extension Schemas](fallback::https://dev.wix.com/docs/sdk/backend-modules/data-extension-schemas/schemas/list-data-extension-schemas) every time a visitor navigates to your UI, to collect and display the user fields.

Coding Examples

Sled Tests

Go Headless

Build Apps

Client

API Preview

Ricos

Develop Websites

REST

Velo

Picasso

GraphQL (Alpha)

Schemas

Schemas 1 0 0

dataExtensionSchema

DataExtensionSchema

Creates a user-defined data extension schema.

import { schemas } from '@wix/data-extension-schema';

async function createDataExtensionSchema(dataExtensionSchema) {
  const response = await schemas.createDataExtensionSchema(dataExtensionSchema);
};

createDataExtensionSchema

import { schemas } from '@wix/data-extension-schema';
import { auth } from '@wix/essentials';

async function myCreateDataExtensionSchemaMethod(dataExtensionSchema) {
  const elevatedCreateDataExtensionSchema = auth.elevate(schemas.createDataExtensionSchema);
  const response = await elevatedCreateDataExtensionSchema(dataExtensionSchema);
}

createDataExtensionSchema (with elevated permissions)

import { createClient } from '@wix/sdk';
import { schemas } from '@wix/data-extension-schema';
// Import the auth strategy for the relevant access type
// Import the relevant host module if needed

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


async function createDataExtensionSchema(dataExtensionSchema) {
  const response = await myWixClient.schemas.createDataExtensionSchema(dataExtensionSchema);
};

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

createDataExtensionSchema (self-hosted)

Manage Data Extensions Schemas

Manage eCommerce - all permissions

Manage Stores - all permissions

Manage Restaurants - all permissions

Manage Stores

[Fully qualified domain name](https://dev.wix.com/docs/rest/articles/getting-started/fqdns).

fqdn

string

options

ListDataExtensionSchemasOptions

Retrieves a list of global and user-defined data extension schemas for a given FQDN.

import { schemas } from '@wix/data-extension-schema';

async function listDataExtensionSchemas(fqdn, options) {
  const response = await schemas.listDataExtensionSchemas(fqdn, options);
};

listDataExtensionSchemas

import { createClient } from '@wix/sdk';
import { schemas } from '@wix/data-extension-schema';
// Import the auth strategy for the relevant access type
// Import the relevant host module if needed

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


async function listDataExtensionSchemas(fqdn, options) {
  const response = await myWixClient.schemas.listDataExtensionSchemas(fqdn, options);
};

listDataExtensionSchemas (self-hosted)

Manage Blog

Manage Bookings Services and Settings

Manage Challenges

Access Verticals by Automations

Set Up Automations

Read Data Extensions Schemas

Manage Events

Manage Portfolio

ListDataExtensionSchemasResponse

Updates a user-defined data extension schema, overriding the existing data.

import { schemas } from '@wix/data-extension-schema';

async function updateDataExtensionSchema(dataExtensionSchema) {
  const response = await schemas.updateDataExtensionSchema(dataExtensionSchema);
};

updateDataExtensionSchema

import { schemas } from '@wix/data-extension-schema';
import { auth } from '@wix/essentials';

async function myUpdateDataExtensionSchemaMethod(dataExtensionSchema) {
  const elevatedUpdateDataExtensionSchema = auth.elevate(schemas.updateDataExtensionSchema);
  const response = await elevatedUpdateDataExtensionSchema(dataExtensionSchema);
}

updateDataExtensionSchema (with elevated permissions)

import { createClient } from '@wix/sdk';
import { schemas } from '@wix/data-extension-schema';
// Import the auth strategy for the relevant access type
// Import the relevant host module if needed

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


async function updateDataExtensionSchema(dataExtensionSchema) {
  const response = await myWixClient.schemas.updateDataExtensionSchema(dataExtensionSchema);
};

updateDataExtensionSchema (self-hosted)

UpdateDataExtensionSchemaResponse

# About the Data Extension Schema API

A data extension schema allows you to define and validate the structure of additional custom fields that can be dynamically added to Wix API objects. This schema acts as a blueprint, describing the properties, data types, and constraints for these custom `extendedFields` fields, based on a [JSON schema](https://dev.wix.com/docs/build-apps/develop-your-app/extensions/backend-extensions/schema-plugins/the-json-schema) as part of the [schema plugin extension](https://dev.wix.com/docs/build-apps/develop-your-app/extensions/backend-extensions/schema-plugins/about-schema-plugin-extensions). For example, a data extension schema can describe custom shipping data added to the [Wix eCommerce Checkout object](https://dev.wix.com/docs/sdk/backend-modules/ecom/checkout/get-checkout).

The Data Extension Schema API enables you to: 
- [Retrieve all the data extension schemas](https://dev.wix.com/docs/sdk/backend-modules/data-extension-schemas/schemas/list-data-extension-schemas) installed on a site.
- [Create](https://dev.wix.com/docs/sdk/backend-modules/data-extension-schemas/schemas/create-data-extension-schema) and [update](https://dev.wix.com/docs/sdk/backend-modules/data-extension-schemas/schemas/update-data-extension-schema) user-defined schemas for a site.

Learn more about [reading and writing schema plugin fields](https://dev.wix.com/docs/build-apps/develop-your-app/extensions/backend-extensions/schema-plugins/about-reading-and-writing-schema-plugin-fields).

### User-defined data extension schemas
A user-defined data extension schema is created when a Wix user creates their own extended fields. This schema is saved under a dedicated `_user_fields` `namespace`. For example, Wix users can add their own fields to the checkout flow in the site's dashboard under **Settings** > **Checkout** > **Checkout form** when they edit the checkout form: 

![Checkout extended fields](./assets/checkoutExtendedField.png)  

The resulting user-defined data extension is saved in the `_user_fields` `namespace`.

## Before you begin
It's important to note the following before starting to code:
- App schema plugin extensions, including their JSON schemas, are created and maintained in an [app dashboard](https://manage.wix.com/studio/custom-apps). This API only supports creating and updating **user-defined** schemas.
- Schema plugin extensions are supported by select [Wix API objects](https://dev.wix.com/docs/build-apps/develop-your-app/extensions/backend-extensions/schema-plugins/about-schema-plugin-extensions#see-also). Always check that the object you would like to extend includes a property named `extendedFields`.
- This API supports retrieving data extension schemas from [multiple `namespaces`](https://dev.wix.com/docs/build-apps/develop-your-app/extensions/backend-extensions/schema-plugins/about-reading-and-writing-schema-plugin-fields#namespaces) in a single call.
- Data extension schemas are supported by select [Wix API service entities](https://dev.wix.com/docs/build-apps/develop-your-app/extensions/backend-extensions/schema-plugins/about-schema-plugin-extensions#see-also). Always check that the service object you would like to extend supports this functionality.
- `namespace` name limitations:
  - Can't include "Wix".
  - Only supports lowercase letters, numbers, hyphens, and underscores.
  - Max length: 164 characters.
  - Once set, `namespace` names can't be changed.

## Use cases
- [Retrieve a list of all data extension schemas for the Wix eCommerce Checkout object](https://dev.wix.com/docs/sdk/backend-modules/data-extension-schemas/schemas/sample-flows#retrieve-a-list-of-all-data-extension-schemas-for-the-Wix-ecommerce-checkout-object)
- [Add fields to a user-defined data extension schema](https://dev.wix.com/docs/sdk/backend-modules/data-extension-schemas/schemas/sample-flows#add-fields-to-a-user-defined-data-extension-schema-for-the-wix-ecommerce-order-object)
  
## Terminology
- **Data extension schema**: A JSON schema defining the data structure of the custom fields to add to a Wix object. 
- **FQDN**: Fully qualified domain name, a unique identifier for a Wix object. Learn more about [FQDNs](https://dev.wix.com/docs/rest/articles/get-started/fqdns).
- **Namespace**: A unique identifier for your app or project. Expected format is @myCompany/myAppName. See limitations in the Before you begin section above.
- **Schema plugin extension**: Specific functionality that extends a Wix object with custom fields, nested in the object called `extendedFields`.
- **User-defined schema**: The schema created when a Wix user creates their own extended fields. This schema is created with the `namespace`: `_user_fields`.


@package_metadata:@wix/data-extension-schema

To use the Schemas API, install the `@wix/data-extension-schema` package.

#### Install the package

Follow the installation instructions for your development environment.

| Development environment | Installation method |
|--|--|
| Wix sites (editor or IDE) | Use the [package manager](https://dev.wix.com/docs/develop-websites/articles/coding-with-velo/packages/work-with-npm-packages-in-the-editor). |
| Wix sites (local IDE) | Run `wix install @wix/data-extension-schema` using the [Wix CLI](https://dev.wix.com/docs/develop-websites/articles/coding-with-velo/packages/work-with-npm-packages-with-the-wix-cli).|
| Blocks apps | Use the same installation method as Wix sites. |
| CLI and self-hosted apps | Run `npm install @wix/data-extension-schema` or `yarn add @wix/data-extension-schema`. |
| Headless sites and apps | Run `npm install @wix/data-extension-schema` or `yarn add @wix/data-extension-schema`. |

#### Import the package

To import the package in your code:

```js
import { schemas } from '@wix/data-extension-schema'
```
  

# Sample Flows

This article shares some possible use cases you could support, as well as an example flow that could support each use case. 
You're certainly not limited to these use cases, but they can be a helpful jumping off point as you plan your implementation.

## Retrieve a list of all data extension schemas for the Wix eCommerce Checkout object 
If your functionality requires access to fields that have been added to an object, you might want to retrieve all of the schemas at once. For example, displaying the returned fields to site visitors. 

1. Collect the FQDN of the relevant Wix API service object that [supports schema plugin extensions](https://dev.wix.com/docs/build-apps/develop-your-app/extensions/backend-extensions/schema-plugins/about-schema-plugin-extensions#see-also). FQDNs are also returned as `entityFqdn` in most events. The Wix eCommerce Checkout FQDN is `wix.ecom.v1.checkout`.
2. Choose the namespaces you would like to retrieve this data for. You can pass multiple namespaces in one call, or leave it blank to retrieve all available namespaces.
3. Call [List Data Extension Schemas](https://dev.wix.com/docs/sdk/backend-modules/data-extension-schemas/schemas/list-data-extension-schemas) with the FQDN and namespace data.
4. Display the returned data as relevant.

## Add a field to a user-defined data extension schema for the Wix eCommerce Order object
Display a site-specific field, such as alcohol by volume (ABV) for whiskey orders, alongside fields from Wix eCommerce Orders, to site visitors.

1.  Collect the FQDN of the relevant Wix API service object that [supports schema plugin extensions](https://dev.wix.com/docs/build-apps/develop-your-app/extensions/backend-extensions/schema-plugins/about-schema-plugin-extensions#see-also). FQDNs are also returned as `entityFqdn` in most events. The Wix eCommerce Order FQDN is `wix.ecom.v1.order`.
1. Call [List Data Extension Schemas](https://dev.wix.com/docs/sdk/backend-modules/data-extension-schemas/schemas/list-data-extension-schemas) with the `wix.ecom.v1.order` FQDN and `_user_fields` namespace to check if a user-defined schema exists.
1. Create or update the `_user_fields` namespace, as relevant:
    1. If no `_user_fields` namespace schema exists, call [Create Data Extension Schema](https://dev.wix.com/docs/sdk/backend-modules/data-extension-schemas/schemas/create-data-extension-schema) with the `wix.ecom.v1.order` FQDN, the `_user_fields` namespace and the new JSON schema.
    1. If a `_user_fields` namespace schema already exists, call [Update Data Extension Schema](https://dev.wix.com/docs/sdk/backend-modules/data-extension-schemas/schemas/update-data-extension-schema) with the `wix.ecom.v1.order` FQDN, the `_user_fields` namespace and the updated JSON schema.
1. Display the user-defined field as relevant.

> **Note**: Once you have added at least one user-defined field, you should call [List Data Extension Schemas](https://dev.wix.com/docs/sdk/backend-modules/data-extension-schemas/schemas/list-data-extension-schemas) every time a visitor navigates to your UI, to collect and display the user fields.


data-extension-schema_schemas

_createdDate

Date and time the schema was last updated.

_updatedDate

currentSizeBytes

number

Schema definition in [JSON schema format](https://dev.wix.com/docs/build-apps/develop-your-app/extensions/backend-extensions/schema-plugins/the-json-schema) with the following [vocab](https://docs.json-everything.net/schema/vocabs/) extension:
```
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://wixapis.com/v1/json-schema/extensions",
"$vocabulary": {
"https://wixapis.com/v1/json-schema/extensions/vocab/data-extensions": true
},
"$dynamicAnchor": "meta",
"title": "Wix' data-extensions vocabulary meta schema",
"type": [
"object",
"boolean"
],
"properties": {
"x-wix-permissions": {
"type": "object",
"description": "list of identity types that are allowed reading schema properties",
"properties": {
"read": {
"type": "array",
"items": {
"type": "string",
"enum": [
"apps",
"owning-app",
"users",
"users-of-users"
]
}
},
"write": {
"type": "array",
"items": {
"type": "string",
"enum": [
"apps",
"owning-app",
"users",
"users-of-users"
]
}
}
}
},
"x-wix-display": {
"type": "object",
"description": "field display properties",
"schema": {
"properties": {
"placeholder": {
"type": "string",
"maxLength": 255,
"description": "placeholder text for input fields"
},
"label": {
"type": "string",
"maxLength": 255,
"description": "label of the input fields"
},
"hint": {
"type": "string",
"maxLength": 255,
"description": "a short explanation that appears next to the input field"
}
}
}
}
}
}
```

jsonSchema

maxLimitBytes

Namespace for this schema. For example, an app creating schemas might use their app name as a namespace.
When a site owner creates a user-defined schema, the namespace is: `_user_fields`.

namespace

Revision number, which increments by 1 each time the schema is updated. To prevent conflicting changes, the existing revision must be used when updating a schema.

revision

DataExtensionSchemaCreatedEnvelope

entity

metadata

EventMetadata

DataExtensionSchemaDeletedEnvelope

DataExtensionSchemaUpdatedEnvelope

DeleteByWhiteListedMetaSiteResponse

hasMore

boolean

Event ID. With this ID you can easily spot duplicated events and ignore them.

A sequence number that indicates the order of updates to an entity. For example, if an entity was updated at 16:00 and then again at 16:01, the second update will always have a higher sequence number.
You can use this number to make sure you're handling updates in the right order. Just save the latest sequence number on your end and compare it to the one in each new message. If the new message has an older (lower) number, you can safely ignore it.

entityEventSequence

Fully Qualified Domain Name of an entity. This is a unique identifier assigned to the API main business entities.
For example, `wix.stores.catalog.product`, `wix.bookings.session`, `wix.payments.transaction`.

entityFqdn

ID of the entity associated with the event.

entityId

Event timestamp in [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) format and UTC time. For example, `2020-04-26T13:57:50.699Z`.

eventTime

eventType

The identification type and identity data.

identity

IdentificationData

instanceId

If present, indicates the action that triggered the event.

originatedFrom

Event action name, placed at the top level to make it easier for users to dispatch messages.
For example: `created`/`updated`/`deleted`/`started`/`completed`/`email_opened`.

slug

Whether the event was triggered as a result of a privacy regulation application
(for example, GDPR).

triggeredByAnonymizeRequest

ID of a site visitor that has not logged in to the site.

anonymousVisitorId

appId

ID of a site visitor that has logged in to the site.

memberId

ID of a Wix user (site owner, contributor, etc.).

wixUserId

identityType

WebhookIdentityType

Extension points within the given entity.

extensionPoints

Additional fields that are hidden by default. For example, fields with `"x-wix-archived": true`.

fields

namespaces

dataExtensionSchemas

OnDataExtensionSchemaCreatedHandler

event

void

OnDataExtensionSchemaDeletedHandler

OnDataExtensionSchemaUpdatedHandler

Returns `x-wix-archived` fields in `DataExtensionSchema.json_schema`.

RequestedField

handler

Triggered when a data extension schema is created.

import { schemas } from '@wix/data-extension-schema';

schemas.onDataExtensionSchemaCreated((event) => {
    // handle your event here
});

onDataExtensionSchemaCreated

import { createClient, AppStrategy } from '@wix/sdk';
import { schemas } from '@wix/data-extension-schema';

const wixClient = createClient({
  auth: AppStrategy({
    appId: 'MY-APP-ID',
    publicKey: 'YOUR_APP_PUBLIC_KEY',
   }),
   modules: {
      schemas,
    },
});

wixClient.schemas.onDataExtensionSchemaCreated((event) => {
    // handle your event here
});

onDataExtensionSchemaCreated (self-hosted)

Triggered when a data extension schema is deleted.

import { schemas } from '@wix/data-extension-schema';

schemas.onDataExtensionSchemaDeleted((event) => {
    // handle your event here
});

onDataExtensionSchemaDeleted

import { createClient, AppStrategy } from '@wix/sdk';
import { schemas } from '@wix/data-extension-schema';

const wixClient = createClient({
  auth: AppStrategy({
    appId: 'MY-APP-ID',
    publicKey: 'YOUR_APP_PUBLIC_KEY',
   }),
   modules: {
      schemas,
    },
});

wixClient.schemas.onDataExtensionSchemaDeleted((event) => {
    // handle your event here
});

onDataExtensionSchemaDeleted (self-hosted)

Triggered when a data extension schema is updated.

import { schemas } from '@wix/data-extension-schema';

schemas.onDataExtensionSchemaUpdated((event) => {
    // handle your event here
});

onDataExtensionSchemaUpdated

import { createClient, AppStrategy } from '@wix/sdk';
import { schemas } from '@wix/data-extension-schema';

const wixClient = createClient({
  auth: AppStrategy({
    appId: 'MY-APP-ID',
    publicKey: 'YOUR_APP_PUBLIC_KEY',
   }),
   modules: {
      schemas,
    },
});

wixClient.schemas.onDataExtensionSchemaUpdated((event) => {
    // handle your event here
});

onDataExtensionSchemaDeleted( )