OpenAPI 3.1
Reference contract and sample endpoints.
KIOWARE DEVELOPER CENTER
Webhooks and Event Schemas
Patterns for subscriptions, webhook signatures, retries, ordering, deduplication and event schemas.
DEVELOPER ASSETS
Technical assets
Postman
Environment variables, auth and sample requests.
Events
Schemas, retry, deduplication and correlation.
Acceptance
UAT checklist and acceptance evidence.
SECURITY BASELINE
Production rules
- Do not embed secrets in Kiosk applications
- Every state-changing command uses an idempotency key
- Every transaction has a trace or correlation ID
- Event consumers handle duplicates and out-of-order delivery
- Production credentials follow a security review
EVENT RELIABILITY
Reliable event-processing principles
Source verification
Validate signature, timestamp and key version before processing.
Deduplication
Persist event IDs or idempotency keys for an appropriate retention window.
Out-of-order handling
Use aggregate versions or sequence numbers where ordering matters.
Fast acknowledgement
Return ACK early, move heavy processing to queues and provide a dead-letter flow.
- Event schemas are versioned with backward-compatibility policy.
- Retry policy has limits, jitter and alert thresholds.
- Payloads contain no secrets and minimize personal data.
- Material events carry a trace ID linked to the originating transaction.