# Account webhooks

Events for account connections, permission loss, notifications, verifications, API changelog entries and test sends.

## Events

### Account

| Event | Description |
| --- | --- |
| [`account.connected`](/webhooks/accounts/account-connected) | An account was connected to a profile |
| [`account.disconnected`](/webhooks/accounts/account-disconnected) | A connected account stopped working or was removed |
| [`account.permissions_changed`](/webhooks/accounts/account-permissions-changed) | An account lost a permission area but stays connected |
| [`account.rate_limited`](/webhooks/accounts/account-rate-limited) | A mailbox entered a sending cooldown |
| [`account.restricted`](/webhooks/accounts/account-restricted) | An account failed its last three publishes with the same account-level error, so publish-now posts to it answer 422 |
| [`account.recovered`](/webhooks/accounts/account-recovered) | A publish succeeded on an account `account.restricted` reported |
| [`account.privacy_request`](/webhooks/accounts/account-privacy-request) | A Shopify merchant asked to export or erase customer or shop data |

### Verification

| Event | Description |
| --- | --- |
| [`verification.approved`](/webhooks/accounts/verification-approved) | The recipient submitted the right code |
| [`verification.failed`](/webhooks/accounts/verification-failed) | The attempts ran out without a correct code |

### API changelog

| Event | Description |
| --- | --- |
| [`api.changelog.published`](/webhooks/accounts/api-changelog-published) | An entry was published to the changelog |

### Notifications

| Event | Description |
| --- | --- |
| [`notification.sent`](/webhooks/accounts/notification-sent) | Built for agents: a post failure or account disconnect we would email, with its text and the API calls that act on it |

### Test

| Event | Description |
| --- | --- |
| [`webhook.test`](/webhooks/accounts/webhook-test) | Zernio sent a test event to an endpoint |

## How it behaves

<Accordions>
<Accordion title="How disconnect detection works" id="how-disconnect-detection-works">

`account.disconnected` has 5 detection paths, from immediate API removals to reconciliation that can lag about a day. The path decides how quickly you hear about it. See the event page for each path.

</Accordion>
<Accordion title="Poll liveness for WhatsApp" id="poll-liveness-for-whatsapp">

Do not read the absence of `account.disconnected` as proof a channel is alive. Poll the [liveness check](/platforms/whatsapp/phone-numbers#liveness-check) or [account health](/platforms/whatsapp/phone-numbers#other-status-endpoints-and-what-they-tell-you).

</Accordion>
<Accordion title="A missing permission fires once per area" id="a-missing-permission-fires-once-per-area">

`account.permissions_changed` fires once per affected area, however many posts fail afterwards. See the event page.

</Accordion>
<Accordion title="notification.sent is the event for agents" id="notification-sent-mirrors-the-emails">

`notification.sent` is built for agents: one event for every post-failure and account-disconnected email we would send, whatever the user's email preferences and even when no email can be sent.

`notification.text` is the email body without the greeting, and `notification.actions` lists the API calls that fix it.

To keep post and account state in sync, use `post.platform.failed`, `post.failed` and `account.disconnected`, which still fire as before. See the event page.

</Accordion>
</Accordions>

## Related

- [Webhooks](/webhooks): endpoints, retries, signatures and routing.
- [Connecting accounts](/guides/connecting-accounts): what fires `account.connected`.
- [Account health](/accounts/get-all-accounts-health): `canPost` and `canFetchAnalytics` per account, on demand.
- [Disconnect an account](/accounts/delete-account): the intentional path.
- [Check a verification code](/verify/check-verification): what fires the verification events.
- [Test webhook](/webhooks/test-webhook): send `webhook.test` on demand.