This document defines how DCKAP Integrator generates, validates, and delivers output data to destination systems — ensuring that all outputs meet the required standards for completeness, accuracy, and timeliness before and after delivery.
2. Output Types
Output Type
Description
Example
API Push (Synchronous)
Record posted directly to destination system REST/SOAP API
Create order in ERP
Batch Delivery
Multiple records delivered in a single API call or file
Bulk inventory update to eCommerce
Webhook Relay
Incoming webhook from source forwarded (transformed) to destination
Real-time stock update
Report / Extract
Scheduled data extract written to file storage or BI endpoint
Daily sales report to analytics
Acknowledgement
Delivery receipt or error response returned to source system
Order confirmation status
3. Pre-Delivery Validation
Output payload validated against the destination system’s accepted schema before delivery.
Mandatory destination fields confirmed to be present and non-null.
PII fields confirmed to be within permissible scope for the destination system.
Idempotency key generated and attached to prevent duplicate delivery.
4. Delivery Policies
4.1 Completeness Policy
All records accepted into the output queue must be delivered — no silent drops are permitted.
Any record that cannot be delivered after all retry attempts is moved to the dead-letter queue and an alert is raised.
Delivery receipts (HTTP 2xx from destination) are required for each record — assumed failure without explicit acknowledgement.
4.2 Accuracy Policy
Field values in the output must match the transformation specification exactly.
Numeric values must not suffer precision loss during delivery serialisation (e.g., floating point rounding).
Character encoding must be UTF-8 for all string outputs.
4.3 Timeliness Policy
Delivery Mode
SLA Target
Breach Alert Threshold
Event-triggered (real-time)
< 60 seconds from source event
> 2 minutes
Scheduled sync
< 5 minutes from schedule trigger
> 10 minutes
Bulk batch
< 30 minutes per 50,000 records
> 60 minutes
Report / extract
Within configured schedule window ± 10 minutes
> 20 minutes past window
5. Post-Delivery Verification
Delivery confirmation is stored in the audit log with timestamp and destination response code.
