Webex for Developers — Webhooks

Publisher

Cisco Systems, Inc. (developer.webex.com)

URL

https://developer.webex.com/calling/docs/api/guides/webhooks

Published

2026-09-10

Updated

unknown

Accessed

2026-09-16

HTTP status

200

License

Cisco proprietary documentation, all rights reserved; no-redistribution; short excerpts and locators only

Source notes citing this source

• Webex developer documentation pages carry a publication timestamp in the embedded page state at documentation.entry.publishDetails.time, an ISO 8601 value that differs between pages fetched in one pass: the webhooks guide reads 2026-09-10, and the provisioning and integration scopes guides read 2026-08-13. field report in context
• Cisco warns that the all event on a firehose webhook covers only created, updated and deleted, and that individual webhooks must still be registered for meetings started and ended and for meeting participant joined and left. in context
• The Webex webhooks resource supports firehose subscriptions in 2 forms, a single resource firehose using the all event and an all resource firehose using all for both resource and event, and Cisco states that only 3 resources support them: memberships, messages and rooms. in context
• The Webex platform webhooks guide is a fourth webhook surface beside the Control Hub alert webhook, the Webex Calling detailed call records webhook and the Cisco devices webhook field reference, and it is the only one of the 4 that publishes a disabling rule, a signature scheme and an instruction for verifying a payload. inferred in context
• Cisco states that if Webex attempts to deliver 100 webhook notifications within 5 minutes and the target server either becomes unreachable or does not respond with an HTTP code in the 2xx range, the webhook is disabled, and that once disabled it is not re-enabled automatically. in context
• A Webex webhook payload omits sensitive content such as message text, because Webex encrypts it with keys available only to the members of the space and the webhook request carries no access token with which to decrypt it, so a receiver that needs the content must make an authenticated request for the full resource using the identifier in the payload. in context
• A disabled webhook is reactivated through the Update a Webhook endpoint with its status set to active, and Cisco states that a webhook re-enabled within 5 minutes of being automatically disabled has a lower threshold for delivery problems and will be immediately disabled again if the server is unreachable or does not respond successfully during that period. in context
• Webex supports 2 webhook signature headers: X-Spark-Signature carries an HMAC-SHA1 signature when the webhook was created with a secret, and X-Webex-Signature provides HMAC-SHA256 and HMAC-SHA512 signatures for supported webhook types, with Cisco recommending the second where it is available and naming the first as the compatibility path for webhook types that do not offer it. in context
• Cisco instructs a webhook receiver to compute the HMAC over the unmodified raw request bytes before parsing or re-serialising the JSON, to compare the expected and received signatures in constant time before processing the payload, and to look the header up case-insensitively because Webex may deliver it in lowercase over HTTP/2. in context
• Cisco states that it is continuously adding infrastructure to the Webex cloud so that listing allowed IP addresses is not practical, and that the shared-secret signature is the technique it introduced to let a receiver verify cryptographically that a request came from Cisco. in context

Cite this source record

APA

WarmTransfer. (2026, September 10). Webex for Developers — Webhooks. WarmTransfer. https://warmtransfer.net/knowledge/sources/cisco-dev-webhooks-guide

BibTeX

@misc{warmtransfer-cisco-dev-webhooks-guide,
  title  = {Webex for Developers — Webhooks},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/sources/cisco-dev-webhooks-guide},
  note   = {Cisco Systems, Inc. (developer.webex.com), accessed 2026-09-16}
}