Commerce · Component · supplier-webhook-ingress
Supplier webhook event ingestion
What it does
Decode, validate and persist hotel supplier notifications for downstream reconciliation.
Core pattern
External callback validation and decoding + persisted acknowledgements
- Input
- Raw supplier callback
- Output
- Persisted event and acknowledgement
Key parameters
| Name | Type | Default | Values |
|---|---|---|---|
| event_kind | — | — | — |
| signature_encryption_configuration | — | — | — |
| deduplication_identity | — | — | — |
| event_type | — | — | — |
| status_mapping | — | — | — |
Maturity and limits
Notify tests and /v1/supplier/whale/notify implementation. Static source inspection only; no runtime, provider, deployment or test-pass claim.
Private baseline without a root license; verify reuse rights. Provider credentials, customer data, supplier terms and explicit execution gates require preservation.
Used in pipelines
Industry tags
- Travel & hotelsSource-supported industry
For work involving destinations, room rates and bookings, use external callback validation and decoding followed by persisted acknowledgements.
- HealthcareTransferable use
For non-clinical resource booking and cancellation coordination, use external callback validation and decoding followed by persisted acknowledgements.
Skills pack
Contract scaffold and deterministic mock
Download · 11KBSHA-256 7932e765c037e2551bd3c001b35ccb8bf7d6a0b74e8103092fadb028cf8a9c25
Related components
-
Aftersales approvals, refunds and replacement orders
Exception intake + human-approved refund or replacement
Working 3 pipelines -
Cruise booking and passenger workflow
Selections and participant records + state and amount history
Working 1 pipeline -
Customer-specific catalogs, pricing, promotions and credit
Segment-aware quotes + promotion budgets and credit checks
Working 1 pipeline -
Cruise inquiries and request tracking
Preference-based inquiry records + numbered tracking and handling
Working 1 pipeline