sub-modules
Webhook Events
Stop polling for what already happened — the event arrives with proof.
Integration teams burn weeks on polling schedules, missed updates, and reconciliation jobs that exist only because nobody told them what changed. Webhook Events tells them: 100+ business moments delivered with signatures, schemas, and idempotency — so consumers react to facts instead of hunting them.
Event families in operation
Each family below emits from the same commit path as the operation itself — events never describe something the ledger did not do.
data Viz
data View
section: stages
Order and Fulfillment
Quote, order, promise, shipment, delivery, and return events with the commercial identifiers attached. Storefronts, 3PLs, and EDI partners consume the same stream instead of polling order status.
Inventory and Warehouse
Receipt, move, count, pick, pack, and shipment events with bin, lot, and serial context. Replenishment and external systems react to stock facts as they validate.
Finance
Invoice, payment, close-stage, and consolidation events with ledger references. Reporting and compliance consumers build from posted facts, never drafts.
Workforce and CRM
Roster, attendance, opportunity, case, and loyalty events with actor and policy context. Scheduling, payroll, and engagement systems stay current without batch exports.
Delivery contract
Subscriptions declare endpoint, families, filters, secret, and retry policy. Deliveries sign with HMAC over the canonical payload, track attempts with backoff, and park poison messages in dead-letter with the failure evidence attached. Idempotency keys make redelivery safe to reprocess.
data Viz
data View
section: delivery
Webhook guarantees
- Signed payloads
- HMAC signatures over canonical bytes with schema versions attached
- Safe redelivery
- Idempotency keys make retries and replays reprocessable without duplication
- Scoped streams
- Family and object filters so endpoints receive only their contract
- Replayable history
- Retained positions rewind missed events after outages or backfills
- section
- capabilities
Webhooks by consumer
Event consumption bends per consumer — same signed envelopes, different reaction stakes.
data Viz
data View
section: industries
Storefronts and 3PLs
Order and shipment events drive storefront status, tracking pages, and 3PL handoffs. Retries with backoff absorb consumer outages without losing the stream.
Finance Systems
Invoice and payment events feed external reporting and compliance tools from posted facts. Schema versions let consumers migrate parsers on their schedule.
Data Platforms
Warehouse and lake ingestion replays history into new consumers for backfill, then follows live positions. Idempotency keys keep replays duplication-free.
Webhook Events questions
Section 1
How do we verify a webhook is genuinely from XRP?
Each payload carries an HMAC signature over canonical bytes plus a schema version. Receivers recompute against the subscription secret — mismatches refuse before any processing.
Section 2
What happens when our endpoint is down?
Deliveries retry with backoff while the position retains. On recovery the stream replays missed events in order; poison messages park in dead-letter with failure evidence instead of blocking the stream.
Section 3
Can we replay history into a new integration?
Yes. Subscriptions rewind from retained positions into sandbox or production endpoints, so new consumers backfill without asking source systems to resend anything.
Section 4
Our security team distrusts inbound webhooks. What do we tell them?
Show them the signature scheme, the schema pinning, and the dead-letter evidence. Every payload is verifiable before processing — which is more than polling ever offered.
data View
section: faqs
content section
value: Integrations stop polling and start reacting: the event arrives with its evidence, the signature proves it, and the idempotency key makes redelivery safe.
Section 7
100+ event families across orders, inventory, finance, workforce, and CRM
Section 8
Signed payloads with schema versions and idempotency keys
Section 9
Family and object-scope filtering per subscription
Section 10
Delivery tracking with retry policy and dead-letter evidence
Section 11
Replay from retained positions after outages
Section 12
Sandbox event replay for integration testing