Webhook Events

Caller identity action required event

Fired when a caller identity waits on you. reason says what: changes_requested (answer the review with PATCH), email_code (the authorizer got a 6-digit code from the carrier; confirm it with the verify-email endpoint), rejected (the carrier rejected it; fix and PATCH), infringement_claim (a third party disputes the name or logo; reply to our email with evidence) or expired (resubmit).

postWebhookbranded_calling.identity.action_required

Payload

idstring

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.

event'branded_calling.identity.action_required'

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

reason'changes_requested' | 'email_code' | 'rejected' | 'infringement_claim' | 'expired'

messagestring

What to do, in words.

Response

Webhook received successfully

Changes

Webhooks have no change history: a webhook is keyed by its event name rather than a path and method, so no recorded change can name it.