Platform capability · Webhooks & Events
One event model for delivery inside the platform and signed webhooks to customers
One event model with two ways to deliver. An app declares the events it sends and receives. Events pass between services inside the platform and are checked against their definition first, and every service gets the code that sends and receives them automatically. Webhook payloads are signed, failed deliveries are retried with increasing delays, and deliveries that still fail are kept so they can be reviewed and sent again. Subscribers manage their own deliveries in a self-service portal, and every event a subscriber can receive has a versioned definition.
Webhooks deliver events to your customers’ systems, outside the platform. The internal event stream delivers events to apps inside the platform. Both come from the same source. An app publishes an event once through the SDK, and the platform delivers it to each subscriber by the right route.
Every payload is signed with HMAC-SHA256, using a secret for each subscriber. A failed delivery is retried after 10, 60 and 300 seconds. If it still fails, it is kept in a failed-delivery queue. Failed deliveries can be sent again by hand or by script. Subscribers receive signed deliveries they can verify, and your operators have a queue they can clear.
Apps declare their events in the app declaration: name, structure, version and examples. The catalog can be read through the API and is shown in the customer portal. Subscribers can see which events exist, what each one contains and which version they use. A deprecation is announced in the same place.
A solution architect will demo the live service against your domain model.