SATIK DEVELOPER DOCS · V1 BETA

What happened after dispatch?

Delivery outcomes add real-world context to your next address check.

Report the final outcome

Report the final delivery result using POST /v1/outcomes. The endpoint is free within rate limits. Send verification_id where possible; ambiguous order IDs are rejected.

Accepted delivery outcomes
Outcome	Meaning
Delivered`delivered`	The shipment reached the customer.
Returned to origin`rto`	The shipment was returned to the sender.
Customer refused delivery`customer_refused`	The customer declined the delivery.
Address issue`address_issue`	An address-related issue affected delivery.
Lost shipment`lost`	The shipment was lost; excluded from the address-history denominator.
Cancelled shipment`cancelled`	The shipment was cancelled; excluded from the address-history denominator.

Deduplicated learning

Each tenant can report one final outcome per verification. Repeated reports return duplicate=true and do not increment counts again. Corrections to an already-final outcome require a support workflow.

Evidence before escalation

History never upgrades an uncertain address to SHIP. Evidence thresholds must be met before it can make a verdict more cautious.

History evidence requirements
Context	Minimum evidence
Area context	At least 30 terminal address-related outcomes.
Unit context	At least 5 unit outcomes.
Excluded outcomes	Lost and cancelled shipments do not dilute the address-history denominator.