> Portal Navigation:
> 
> - Append `.md` to any URL under `https://dev.wix.com/docs/` to get its markdown version.
> - Pages are either content pages (article or reference text) or menu pages (a list of links to child pages).
> - To get a menu page, truncate any URL to a parent path and append `.md` (e.g. `https://dev.wix.com/docs/sdk.md`, `https://dev.wix.com/docs/sdk/core-modules.md`).
> - If a reference page seems to be missing its schema (parameters, return types, or type definitions), append `?schema=true` to its `.md` URL (e.g. `https://dev.wix.com/docs/contexts/contexts/stores/category-info/use-category-info-context.md?schema=true`).
> - Top-level index of all portals: https://dev.wix.com/docs/llms.txt
> - Full concatenated docs: https://dev.wix.com/docs/llms-full.txt

## Resource: About Account-Level Webhooks

## Article: About Account-Level Webhooks

## Article Link: https://dev.wix.com/docs/overview/backend-services/about-account-level-webhooks.md

## Article Content:

# About Account-Level Webhooks

Account-level webhooks notify your server when something changes in your Wix account. Unlike [backend events](https://dev.wix.com/docs/overview/backend-services/events.md), 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](https://support.wix.com/en/article/wix-enterprise-an-overview) and [Wix Channels](https://support.wix.com/en/article/wix-channels-dashboard-overview) partners.

## How account-level webhooks work

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](https://jwt.io/), 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.

## How they differ from backend events

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](https://dev.wix.com/docs/overview/backend-services/events.md). | 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](https://dev.wix.com/docs/overview/backend-services/events.md). | 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. |

## Available events

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](https://dev.wix.com/docs/api-reference/account-level/about-account-level-apis.md) section of the API Reference, listed under each applicable API. For example, the [Folder Created](https://dev.wix.com/docs/api-reference/account-level/sites/site-folders/folder-created.md) event is documented under **Sites** > **Site Folders**.

## Webhook logs

The **Logs** tab on the **Webhooks** page tracks webhook deliveries over the past 30 days. Each log entry includes:

- Response status
- Event name
- Callback endpoint
- Instance ID
- Timestamp

Use logs to confirm successful deliveries or debug issues with your endpoint.

## Child account events

A [child account](https://dev.wix.com/docs/api-reference/account-level/user-management/accounts/accounts/about-accounts.md#terminology) 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.

## See also

- [Handle Account-Level Webhooks](https://dev.wix.com/docs/develop-websites-sdk/code-your-site/build-a-custom-backend/backend-events/handle-account-level-webhooks.md): Verify the signature and read the payload on your server.
- [About the Structure of Webhooks](https://dev.wix.com/docs/api-reference/articles/work-with-wix-apis/platform/about-the-structure-of-webhooks.md)
- [Events](https://dev.wix.com/docs/overview/backend-services/events.md)
- [Events and webhooks](https://dev.wix.com/docs/overview/backend-services/events.md#events-and-webhooks): How the same events reach your code on each development path.