SATIK DEVELOPER DOCS · V1 BETA

Every flag has a reason.

Understand what needs attention and what to do next. Each reason also has a stable API code for your integration.

Address details

Details that help identify the delivery location.

Address details: reasons and next steps
Reason	Meaning and next step
Missing flat or house number`missing_unit`	Ask for the flat, house, or shop number, or the building name.
Incomplete address`address_incomplete`	Request the full delivery address so the location can be checked.
Only a landmark provided`landmark_only_routing`	Ask for the building or street details in addition to the landmark.
Building not confirmed`unconfirmed_building`	Review the location manually. The available validation does not confirm the delivery building.
Plus Code detected`plus_code_fallback`	A Plus Code was found in the input. Confirm the full delivery address; a location code alone does not verify a building.

Changes or mismatches found during address validation.

Corrections: reasons and next steps
Reason	Meaning and next step
Pincode corrected`wrong_pincode_replaced`	Confirm the pincode suggested by the address validation provider with the customer.
Pincode and locality may not match`pincode_locality_mismatch`	Confirm the locality and pincode together before dispatch.
Address details added`inferred_components`	Ask the customer to confirm details inferred by the validation provider.
Spelling corrected`spell_corrected`	The provider corrected the spelling of an address detail.

Additional context from recorded deliveries and the information provided.

History and input: reasons and next steps
Reason	Meaning and next step
No delivery history yet`no_history`	Informational only: there are no recorded delivery outcomes for this area. This alone does not mean the address is unsafe.
Elevated return history`high_rto_area`	Recorded returns for this area or delivery unit met a review threshold. Follow the recommended next step for this result.
Conflicting address details`suspicious_components`	Check conflicting input, such as multiple different pincodes, with the customer.
Phone number needs checking`phone_invalid`	The optional phone number is invalid. Confirm it separately; a valid phone number does not validate an address.