Events & webhooks
Design for duplicate delivery—but only against a published subscription contract.
No public subscription contract yet
A public Events and Webhooks API is on the roadmap. This portal does not invent subscription paths, signing headers, event names, or delivery guarantees. Internal event streams are not partner APIs.
Integration design checklist
Before enabling a webhook integration, require a versioned contract for event ownership and data class, subscription scope, signature input and rotation, duplicate handling, ordering limits, retries, replay, and retention.
Persist an event’s documented identity before applying side effects. Plan for duplicate or out-of-order delivery where the eventual contract permits it. An HTTP delivery receipt should not be confused with successful business processing.