Backend extensions enable apps to customize Wix's backend business logic and add value to site builders and apps.
The data collections extension allows your app to automatically create CMS data collections when it's installed on a site. You configure the collection schemas and optional initial data in a JSON configuration file. When a Wix user installs your app, the collections are automatically created in the site's CMS.
This extension automatically enables the site's code editor, which is required for the Wix Data APIs to work. This means your app can use Data APIs to read and write data in the collections without requiring Wix users to manually enable the code editor.
For example, a small business app might use a data collections extension to create a "Customer Feedback" collection that stores customer reviews and ratings. The app could pre-populate the collection with sample feedback entries to help Wix users understand how the app works.
Service plugins are APIs that are defined by Wix, which you can choose to implement. When you implement a Wix service plugin in your app, you become a service provider. Wix then calls your service during one or more specified flows, waits for your response, and then continues the flow based on your response.
For example, a Local Delivery Provider app may implement the Restaurants Local Delivery service plugin, which includes a Get Delivery Estimate endpoint. Wix then calls this provider when they need to fetch applicable delivery estimates during a customer’s checkout flow.
Schema plugins are field extensions to Wix’s objects that you can use to enrich and extend Wix’s data. Every Wix API has a service object with predefined fields, that can’t be removed or changed. But sometimes there is a business need to include additional data that Wix doesn’t save by default.
For example, an app managing bookings and equipment rental for outdoor adventure companies may want to include equipment rental data as part of the booking. With a schema plugin, the app can add an equipment field to the Bookings Service object. The equipment field becomes a part of the object, and the app can retrieve and manage it with the Bookings APIs.
Notifications allow you to send predefined messages with customizable data to your app's users in their site dashboard and/or the Wix Owner mobile app. This can be a useful way to alert users about important updates and events.
For example, an app managing a business’ social media presence may want to notify site builders about new media posts they are referenced in, likes, and so on.
Automations allow you to predefine functionality of multiple types, based on triggers and actions. Automations leave site owners free to focus on their business, instead of having to deal with the details of running their site.
For example, an app managing a business' community building tasks might automate a welcome email to everyone who signs up for the site's newsletter or purchases a product.
API extensions let you expose backend logic that your app's frontend can call. The mechanism depends on your framework: the current Wix CLI uses HTTP endpoints, while Wix Blocks and the legacy Wix CLI for Apps use web methods or HTTP functions.
For example, an app may collect feedback from site visitors using frontend code and save the feedback in a database using backend code.
Learn more about backend API extensions.
Events are triggered when specific conditions on your app or a user's site are met. Using event extensions, you can write code that runs when an event occurs.
For example, an event might be triggered when a booking is confirmed. You can implement logic, such as sending a booking confirmation email, when the event is triggered.
An app namespace is a unique identifier for your app. Some backend extensions, such as data collections and schema plugins, require an app namespace. You set the namespace the first time you create an extension that requires one, and you can't change it after that.
To view your app namespace: