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

Example

{
  "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.

FieldType / meaning
contactIdResolved WATI contact identifier.
waId / phonePhone-related identifiers when supplied/resolved; do not fabricate them for a BSUID-only contact.
nameName/username supplied in the inbound identity data.
bsuid / parentBsuidOptional business-scoped identity values; not cross-channel identifiers.