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

# Contact Deleted Webhook Examples

> Handle contact deletion events.

<Note>For the exhaustive schema-derived catalog, see [all examples](/en/api-reference/guides/examples/webhook-examples/webhook-payload-examples).</Note>

## What it is

Handle contact deletion events.

## 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.

```http theme={"theme":{"light":"github-light","dark":"github-dark"}}
HTTP/1.1 200 OK
```

<Note>For endpoint setup, signature validation, and retry behavior, see [Configure webhooks](/en/api-reference/guides/api-fundamentals/configure-webhooks).</Note>

Prerequisites

* The webhook endpoint URL should be provided by your server instead of YCloud. **Make sure to replace the URL with your actual webhook endpoint URL.**
* **Make sure that your webhook endpoint is listening for the appropriate event types.** See also [Configure Webhooks](/en/api-reference/guides/api-fundamentals/configure-webhooks), [Retrieve a webhook endpoint API](/api-reference/webhook-endpoints/retrieve-a-webhook-endpoint).

Occurs when a contact is deleted. The webhook payload contains minimal contact information that was deleted.

## Basic Contact Deleted Example

### Request

```json theme={"theme":{"light":"github-light","dark":"github-dark"}}
{
  "id": "evt_3456789012",
  "type": "contact.deleted",
  "apiVersion": "v2",
  "createTime": "2024-01-01T12:00:00.000Z",
  "contactDeleted": {
    "id": "1824266594102064128",
    "nickName": "John Doe",
    "phoneNumber": "+16315551111",
    "updateTime": "2024-01-01T12:00:00.000Z"
  }
}
```

### Response

Acknowledge the delivery after durably accepting the event.

```http theme={"theme":{"light":"github-light","dark":"github-dark"}}
HTTP/1.1 200 OK
```

### Explanation

* **Minimal Information**: The `contactDeleted` object contains only essential information: `id`, `nickName`, `phoneNumber`, and `updateTime`.
* **Null Values**: The `nickName` field may be `null` if the contact didn't have a nickname set.
* **Update Time**: The `updateTime` reflects when the contact was last modified before deletion.
* **Contact ID**: The `id` field contains the unique identifier of the deleted contact for reference.
* **Phone Number**: The `phoneNumber` is always present and formatted in E.164 format.


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