Webhooks
The order engine does not push events to subscriber endpoints today. There is no subscription registry, no per-event-type subscription and no signed delivery for order, payment or group events.
What to use instead
Poll the outbox by sequence. It gives the guarantees a webhook consumer would need:
| Need | How the outbox provides it |
|---|---|
| No missed events | Events are written in the same transaction as the change; afterSeq resumes exactly where you stopped. |
| No duplicates | Each event has an eventId; replaying from a stored sequence is safe when processing is idempotent on it. |
| Ordering | Strictly increasing seq per tenant. |
| Filtering | type and subjectRef query parameters. |
| Back-pressure | You choose the polling interval and page size. |
An integration layer such as MuleSoft runs this as a scheduled flow: poll, transform, deliver to Salesforce (platform events, Service Cloud records) or other consumers, then store the last sequence.
Related capability in the platform
Kaptio's operational alerting already sends signed webhooks (an X-Kaptio-Signature header: t=<unix seconds>,v1=<HMAC-SHA256 of "<t>.<body>">). This is used for alert notifications, not for order events.