What a Webex webhook guarantees

Verified 2026-09-15 · 17 claims · sources tier 2 · 3 disputed

Also known as Notifications in Control Hub, reportId.

The Control Hub notifications webhook and the Webex Calling detailed call records webhook operate as distinct mechanisms with different configuration models, separate setup surfaces, and different payloads 14. Neither documentation article references the other 14.

Delivery behaviors and reliability

Neither webhook documentation article states a retry mechanism, backoff schedule, delivery ordering, signature scheme, or disabling behavior after repeated delivery failures 3. The terms retry, backoff, delivery ordering, signature scheme, and disabling behavior appear 0 times in both articles 3. Cisco states that the webhooks reliably deliver records, notes that duplicate records may arrive when the system replays records, and places responsibility for de-duplication on the consumer 9. A secret token is optional across both webhook types, and both sources refer readers elsewhere for its operation rather than documenting it directly 10.

Control Hub notifications webhook

Webhook delivery is supported only for select alert categories 2. Out of approximately 12 named alert types, 5 offer webhook delivery, at least 5 do not, and 1 type lists no delivery channel 2. In the field, the article accessed as Enable webhooks for alerts in Control Hub is served under the title Notifications in Control Hub, contains no heading matching the former title, and uses the word alert 234 times compared to 40 mentions of webhook 5.

Sources disagree on proactive alert delivery channels: the proactive alerts section states notifications are delivered through email, Webex App spaces, or both, but its own procedural steps 3 sentences later state a webhook can be chosen if webhooks are enabled at the organization level 7. Sources disagree on webhook schemas as well, publishing 2 incompatible payload schemas that share 5 field names and vary in the casing of the subtype field 13. In the field, none of the 3 webhook payload examples in the notifications documentation parse as valid data: the introductory example ends with a trailing comma, and 2 per-alert examples open on a bare data key lacking an enclosing brace 6.

The configuration steps to define the organization-wide webhook callback URL name no administrator role, and the word role appears 0 times in the notifications article even though other alert categories in that text specify required roles 4. The notifications documentation also points to a Cisco devices webhook field reference in a separate article, representing a third webhook surface distinct from notifications and detailed call records 11.

Webex Calling detailed call records webhook and pull interfaces

Sources disagree on the administrative role required for detailed call records, as the article names the partner role 3 different ways across 3 passages while maintaining a single scope 1.

The documentation gives no retention window for the webhook itself; the 30-day availability window applies strictly to the reconciliation and records pull interfaces, which serve to retrieve records missed by a webhook listener 12. These pull interfaces enforce specific operational limits 8:

See also

See also Control Hub notifications and threshold alerts. See also Webex Calling CDR schema and access. See also What the Webex Calling detailed call history records.

Applicability

Across the claims in this article, the evidence covers Cisco Webex Calling, verified as of 2026-09-15. The deployment model is not covered by any claim in this article.

What remains uncertain

Whether the platform retries a failed webhook delivery is not covered by any claim in this article. Any route to call records older than 30 days is not covered by any claim in this article. Which of the 2 published alert payload schemas is real is not covered by any claim in this article. The Cisco devices webhook field reference is not covered by any claim in this article.

WarmTransfer. (2026, September 15). What a Webex webhook guarantees. WarmTransfer. https://warmtransfer.net/knowledge/webex-calling-webhook-delivery

@misc{warmtransfer-webex-calling-webhook-delivery,
  title  = {What a Webex webhook guarantees},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/webex-calling-webhook-delivery},
  note   = {Verified 2026-09-15}
}