diff --git a/docs/content/advanced/backend/subscribers/events-list.md b/docs/content/advanced/backend/subscribers/events-list.md index 37a954fc61..7576991bd6 100644 --- a/docs/content/advanced/backend/subscribers/events-list.md +++ b/docs/content/advanced/backend/subscribers/events-list.md @@ -1454,7 +1454,7 @@ In one case, when the `/admin/products/{id}` endpoint is used to update the prod ```js { id, //id of product - field //an array of field names that were updated + fields //an array of field names that were updated } ``` @@ -1681,6 +1681,111 @@ Object of the following format: +## Sales Channel Events + +This section holds all events related to sales channels. + +:::note + +As of Medusa v1.3.5, Sales Channels are available but guarded by a feature flag. To use Sales Channels, add the following environment variable: + +```bash +MEDUSA_FF_SALES_CHANNELS=true +``` + +Then, run the [migrations](../migrations.md#how-to-run-migrations). + +::: + +
| +Event Name + | ++Description + | ++Event Data Payload + | +
|---|---|---|
| + +`sales_channel.created` + + | ++ +Triggered when a sales channel is created. + + | ++ +Object of the following format: + +```js +{ + id //string ID of sales channel +} +``` + + | +
| + +`sales_channel.updated` + + | ++ +Triggered when a sales channel is updated + + | ++ +Object of the following format: + +```js +{ + id, //string ID of sales channel +} +``` + + | +
| + +`sales_channel.deleted` + + | ++ +Triggered when a sales channel is deleted. + + | ++ +Object of the following format: + +```js +{ + id //string ID of sales channel +} +``` + + | +