wix_self_hosted_embedded_script

You can self-host a Wix embedded script by deploying an API to handle /install and /uninstall webhooks, registering the script via REST, and serving widget payloads from your database for client-side rendering. This removes the need for third-party hosting.

A webhook-driven Wix embedded script installation automates deployment by using /install and /uninstall webhook endpoints to upsert installations and register the script via the Wix API, allowing dynamic widget content from a database without manual setup.

Local HTTPS development for a Wix embedded script requires configuring a local server to handle webhook installations, REST script registration, and client-side widget rendering. This end-to-end workflow verifies the DB-driven widget on the Wix storefront before deployment.

Yes, a database is required to store and serve the widget payload. The architecture uses a REST endpoint to fetch dynamic widget content from the database, which the client script then resolves and renders on the Wix storefront.

The client script renders a DB-driven widget by resolving the appInstanceId and fetching the widget payload from a REST endpoint. The server retrieves this dynamic content from the database, and the client script renders the UI on the Wix storefront.

Limitations include maintaining your own API for /install and /uninstall webhooks, managing the REST endpoint for script registration, and ensuring the client script correctly resolves appInstanceId. You must also handle database synchronization for widget payloads independently.