Call Capabilities & locations so you know which services, warehouses, payments, and service locations this org actually offers.
For chat / AI bookings: ensure service locations (and warehouses) exist in the dashboard so the bot can peep coordinates instead of guessing — see Capabilities & locations.
Delivery services must be enabled in dashboard settings (API create rejects disabled serviceKind).
Add allowed image hosts under API & Webhooks.
Package photos must be https:// URLs on those hosts. Kilo downloads them and stores them. Private IPs are blocked.
pickup (rider goes to an address) or warehouse (needs warehouseId)
pickupCoords / deliveryCoords
Map coordinates — required for routing. Prefer copying from a service location’s coords or a warehouse’s lat/lng (bots rarely know pins)
packageImages
0–6 HTTPS image URLs from allowlisted hosts. Required (min 1) for pickup_delivery and for errand when errandMode is photo (reference photos). Optional for at_place / link errands
customerCollectionMethod
cash_on_delivery or online_checkout (must be allowed in your settings)
isPODEnabled + podAmount
Cash to collect from the receiver (only if enabled for your fleet)
Save this. Use it for get / cancel / matching webhooks.
access_code
Secret code baked into the tracking link.
tracking.url
Full link to share with the customer (live map + OTP page).
tracking.path
Same page as a path only (if you build your own host).
rider_assigned
true if Auto-dispatch already matched a rider (status will often be matched).
If Customer delivery messages are on, Kilo may also text the tracking link. If they are off, you should paste tracking.url into your WhatsApp/SMS reply.