Skip to main content
For the exhaustive schema-derived catalog, see all examples.

​
What it is

Handle WhatsApp group creation and deletion results.

​
Before you begin

  • Create a public HTTPS endpoint in your application.
  • Configure a YCloud webhook endpoint for the event types you need.
  • Store the endpoint signing secret securely.
  • Make event processing idempotent.

​
How it works

YCloud sends an HTTP POST request when the event occurs. Verify the signature, durably record the event, return a 2xx response, and process slow work asynchronously.

​
Request

The scenarios below show requests delivered to your webhook URL. Treat the event id as the delivery identifier and use type to route the payload.

​
Response

Return a 2xx status after accepting the event.
For endpoint setup, signature validation, and retry behavior, see Configure webhooks.

​
Group Created

When a WhatsApp group is successfully created, you will receive a webhook with the following payload structure:

​
Request

​
Response

Acknowledge the delivery after durably accepting the event.

​
Explanation

Route the event by type, deduplicate it by id, and move slow or failure-prone work to an asynchronous processor.

​
Group Deleted

When a WhatsApp group is deleted, you will receive a webhook with the following payload structure:

​
Request

​
Response

Acknowledge the delivery after durably accepting the event.

​
Explanation

  • type: Always whatsapp.group.lifecycle_update for group lifecycle events
  • whatsappGroup: Contains the group lifecycle result details
    • field: Always group_lifecycle_update
    • type: The lifecycle action, such as group_create or group_delete
    • requestId: The request ID returned by the asynchronous group API operation
    • status: The normalized result status, such as created, deleted, or failed
    • groupId: The WhatsApp group ID
    • inviteLink: The group invite link, included when group creation succeeds
    • dedupeKey: Idempotency key for deduplicating group lifecycle webhook events