> ## Documentation Index
> Fetch the complete documentation index at: https://docs.wavix.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Whatsapp sender changed

> Wavix sends these events to your webhook of the `senders` group when the registration status or quality rating of one of your senders changes, so you learn that a sender is connected, restricted, or banned without polling it. Wavix reads the status and quality rating of senders from the provider every 15 minutes, so an event can arrive up to 15 minutes after the change. A test event you send to the webhook arrives here too.

Each change is a separate event, and `type` names it, so your server keeps its copy of a sender's status and quality rating current.

**Behavior:** Return a 2xx status within 10 seconds to acknowledge the event; Wavix doesn't follow redirects, so a 3xx response counts as a failed attempt. After a failed attempt, Wavix retries about 5 seconds, 30 seconds, 2 minutes, 10 minutes, 1 hour, 6 hours, and 24 hours later, up to 8 attempts in total; a `test` event isn't retried. Events can arrive more than once and out of order, so discard repeats by `id` and keep the state from the event with the latest `timestamp`.

**Requires:** A webhook of the `senders` group. A disabled webhook gets only test events. Its URL must use `https`, have a valid TLS certificate, and resolve only to public addresses that Wavix allows. If the host resolves to another address at send time, Wavix doesn't send the event and doesn't retry it. Verify every request as the [Standard Webhooks](https://www.standardwebhooks.com/) specification describes, with one of its libraries or by hand. The `webhook-signature` and `webhook-timestamp` headers give the steps.

**Limits:** [List WhatsApp events](https://docs.wavix.com/api-reference/whatsapp/list-whatsapp-events) keeps each event except `test` for 30 days, so you can catch up on events your server missed within that time.



## OpenAPI

````yaml https://wavix.github.io/wavix-openapi/wavix-api.yaml webhook WhatsAppSenderChanged
openapi: 3.1.0
info:
  title: Wavix APIs
  description: >-
    Wavix provides robust APIs that let you integrate voice and text messaging
    features directly into your app. Send text, place calls, and access detailed
    reports  programmatically.
  termsOfService: https://wavix.com/terms-and-conditions
  license:
    name: MIT
    identifier: MIT
  contact:
    name: Wavix
    url: https://wavix.com
    email: support@wavix.com
  version: 2.0.0
servers:
  - url: https://api.wavix.com
    description: https://api.wavix.com
    variables: {}
security:
  - bearerAuth: []
tags:
  - name: SIP trunks
    description: SIP trunks
  - name: Buy
    description: Numbers
  - name: Cart
    description: Numbers
  - name: My numbers
    description: Numbers
  - name: Billing
    description: Billing, transactions, and invoices
  - name: Profile
    description: Account profile and customer information
  - name: CDRs
    description: Call detail records and call history
  - name: Speech Analytics
    description: Call transcription and speech analytics
  - name: SMS and MMS
    description: Messaging
  - name: Number Validator
    description: Phone number validation
  - name: Link shortener
    description: Short link and click metrics
  - name: 2FA
    description: Two-factor authentication
  - name: 10DLC
    description: 10DLC Campaigns and Brands
  - name: API Keys
    description: API key management
  - name: Call webhooks
    description: Webhook configuration for call events
  - name: Call control
    description: Programmable Voice
  - name: Call streaming
    description: Real-time call audio streaming over WebSocket
  - name: Call recording
    description: Call recording
  - name: Sub-accounts
    description: Sub-account management
  - name: Voice campaigns
    description: Outbound voice campaigns
  - name: Wavix Embeddable
    description: WebRTC embeddable widget
  - name: WhatsApp
    description: WhatsApp senders, templates, messages, webhooks, and events
  - name: WhatsApp webhook payloads
    description: >-
      Message, template, sender, and marketing preference events Wavix posts to
      your WhatsApp webhooks
paths: {}
components:
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      description: >
        Wavix API key. Pass as `Authorization: Bearer <api_key>`. Keys support
        per-resource scopes (none / read / write). See [Restricted keys and
        scopes](https://docs.wavix.com/api-reference/authentication#restricted-keys-and-scopes).

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.