Account-level webhooks notify your server when something changes in your Wix account. Unlike backend events, which respond to activity on a single site, account-level webhooks cover operations that span your entire account, such as site creation, folder management, and team member updates.
The events aren't tied to a site editor. A webhook for the account covers sites built in Studio Two, Wix Studio, and Wix Editor.
Note: Account-level webhooks are available only for Wix Enterprise and Wix Channels partners.
When you subscribe to an account-level webhook, Wix sends a POST request to your callback URL each time the subscribed event occurs. The request body contains the event data as a JSON Web Token, or JWT, signed with a key pair so you can verify the request is from Wix.
You subscribe to webhooks and manage them from the Webhooks page in your Wix Studio workspace, under Settings > Webhooks. That page is part of the account workspace, not a site editor.
The following table compares backend events with account-level webhooks:
| Backend events | Account-level webhooks | |
|---|---|---|
| Scope | Single site | Entire account |
| Handler location | Site backend code. The file and editor differ by development path. See Events. | Your own external server |
| Payload format | JavaScript event object | Signed JWT |
| Availability | Sites, apps, and headless projects. The handler depends on the development path. See Events. | Enterprise and Channels partners only |
| Headless projects | Wix-managed: event extensions. Self-managed: webhooks. | Self-managed: your own server, alongside the project's site webhooks. |
Account-level webhook events cover account operations including site management, folder organization, and team collaboration. You can find available events in the Account Level APIs section of the API Reference, listed under each applicable API. For example, the Folder Created event is documented under Sites > Site Folders.
The Logs tab on the Webhooks page tracks webhook deliveries over the past 30 days. Each log entry includes:
Use logs to confirm successful deliveries or debug issues with your endpoint.
A child account is a Wix account that was created by another account, known as the parent account. For example, a website reseller might create child accounts for their customers while retaining a relationship to those accounts.
If your account is a parent account, events from your child accounts automatically propagate to your callback URL alongside your own account's events. To distinguish between them, compare the following fields in the webhook payload:
accountId: The account that owns the webhook subscription, which is the parent account.targetAccountId: The account where the event actually occurred.When both values match, the event originated in your own account. When targetAccountId differs from accountId, the event came from a child account.
Last updated: 9 November 2026