---
updatedAt: 2026-11-02T11:10:56.000Z
agentTools:
  projectIndex: https://docs.wati.io/llms.txt
---

# Contact Request Response

Contact Request Response — current payload, usage and account requirements.

`eventType`: `contactRequestTyping`. A WhatsApp contact card returned from a contact-information request was resolved. This applies to accounts using WhatsApp business-scoped identities: the first returned contact must have origin=contact\_request. Ordinary unsolicited contact cards do not qualify. Despite the historical event name, this is a contact-sharing response, not a typing-state/keystroke stream.

Use this documented event only when it is registered by your workspace's [event-types API](https://docs.wati.io/reference/listwebhookeventtypes) and the relevant product/channel is available on your account. Registration alone is not a delivery guarantee; verify an actual permitted event reaches your enabled subscription. Acknowledge promptly with a successful 2xx; process idempotently and allow duplicate/out-of-order delivery. Do not assume a universal event UUID, fixed retry schedule or signing scheme. See [webhook setup and recovery](https://docs.wati.io/reference/introduction-1).

## Example

```json
{
  "eventType": "contactRequestTyping",
  "contactId": "<contact-id>",
  "waId": "15551234567",
  "phone": "15551234567",
  "name": "Example user",
  "bsuid": "<business-scoped-user-id>"
}
```

The example is illustrative, not an exhaustive list of fields or possible outcomes. Null/absent values must be handled.

| Field                 | Type / meaning                                                                                    |
| --------------------- | ------------------------------------------------------------------------------------------------- |
| `contactId`           | Resolved WATI contact identifier.                                                                 |
| `waId / phone`        | Phone-related identifiers when supplied/resolved; do not fabricate them for a BSUID-only contact. |
| `name`                | Name/username supplied in the inbound identity data.                                              |
| `bsuid / parentBsuid` | Optional business-scoped identity values; not cross-channel identifiers.                          |