Webhooks for Groups API | Developer Documentation
Webhooks for Groups API
Updated: Feb 11, 2026
In order to receive webhook notifications for metadata about your groups, please subscribe to the following webhook fields:
group_lifecycle_updategroup_participants_updategroup_settings_updategroup_status_update
group_lifecycle_update webhooks
A
group_lifecycle_update webhook is triggered when a group is either created or deleted.Group create succeed
Group create fail
Delete group succeed
Delete group fails
group_participants_update webhooks
A
group_participants_update webhook is triggered when a WhatsApp user joins a group with an invite link, requests to join a group, cancels their request, or when one or more join requests are approved.User joined group using invite link succeed
User accepts or cancels join request
GROUP_REQUEST_TYPE is set to group_join_request_created.For cancel requests: GROUP_REQUEST_TYPE is set to group_join_request_revoked.
Group participant remove succeed
Group participant remove with participants partially fails
Group participant remove fails
Group participant leaves webhook
This webhook is sent when a group participant leaves the group. The
initiated_by field and only the wa_id in the removed_participants list will point to the participant who left the group.group_settings_update webhooks
Group settings update succeed
Group settings update partial fail
Group settings update total fail
group_status_update webhooks
WhatsApp uses advanced machine learning technology to evaluate group information including group subjects, profile photos, and group descriptions. We also provide simple options for users to make reports to us from any chat.
We may prevent further activity in chat groups to comply with our legal obligations. We may also prevent further chat activity when a group admin is in violation of our Terms of Service?.
You may receive a webhook if a group you manage is suspended. You may also receive a webhook if a suspended group you manage becomes clear of suspensions.
Group suspended
Group suspension cleared
Group Message Status Webhooks
When you send messages to a group, you will receive a status webhook when the message is sent, delivered, and read. Instead of sending multiple webhooks for each status update, we may send an aggregated webhook.
There are two types of aggregated message status webhooks you can receive.
Multiple Participants, Single Message
If you send a message and are set to receive several
read or delivered statuses from participants, we will send you a single, aggregated webhook that contains multiple status objects.Each webhook you receive will be in reference to a single message sent to a single group and a single status type, i.e single group, single status by multiple participants for a single message.
Aggregated group message status
Multiple Messages, Single Participant
If you send multiple messages to a group and are set to receive several 'read' or
delivered statuses from a single participant, we may send you a single, aggregated webhook that contains multiple status objects.Each webhook you receive will be in reference to multiple messages sent to a single group and a single status type, i.e single group, single status by single participant for multiple messages.
Aggregated group message status
Group message delivered
Pricing information
Status messages webhooks that contain pricing information will have:
CONVERSATION_CATEGORY set to one of: group_marketing - Indicates a marketing conversation.group_utility - Indicates a utility conversation.group_service - Indicates a service conversation.IS_BILLABLE set to one of: true - Indicates a billable conversation.false - Indicates a non-billable conversation.PRICING_MODEL set to PMP.