# call.permission_request

A WhatsApp user accepted or rejected your call-permission request.

### When it fires

Independent of any call: it reports a reply to a permission prompt. Meta permits a business-initiated call only after the consumer taps Allow, and the accept can land days before the call.

### Payload notes

`response` is `accept` or `reject`. Also carries the user's number, whether the grant is permanent, and the expiry when it is not.




**Payload for `call.permission_request`:**

- **test** `boolean`: Always true when present: only a sample sent by POST /v1/webhooks/test with an event carries it. Real deliveries never do.
- **id** (required) `string`: Stable webhook event ID: the dedupe key, also sent as the X-Zernio-Event-Id header and identical on every retry and redelivery. It identifies the event only, never an account or other resource.
- **profiles**: `WebhookProfiles` - See schema definition
- **event** (required) `string`: No description - one of: call.permission_request
- **permission** (required) `object`: 
  - **from** `string`: Consumer wa_id who replied
  - **response** `string`: No description - one of: accept, reject
  - **isPermanent** `boolean`: No description
  - **expirationTimestamp** `string` (date-time): Present only when temporary
  - **responseSource** `string`: Meta's response source, typically `user_action`
- **account** (required): `InboxWebhookAccount` - See schema definition
- **timestamp** (required) `string` (date-time): UTC time at which Zernio generated this event (set once when the event payload is built, before delivery is queued). Retries and redeliveries keep the original value, so it reflects the event, not the delivery attempt.