Guides
Delivery fleets
The kitchen owns the order up to ready; the fleet owns it after. Let’s Pizza joins the two.
The flow#
- Branch → Let's PizzaOrder ready
- Let's Pizza → Your systemA delivery job
order.ready - Your system → Let's PizzaThe rider has the food
status: out_for_delivery - Your system → Let's PizzaDelivered (or failed, with a reason)
status: delivered - Your system → Let's PizzaCash collected at the door
POST …/events
The rules#
- You report road statuses only: out_for_delivery · delivered · delivery_failed.
- Delivery failed carries a reason: customer unreachable, wrong address, refused, accident or damage, other.
- Cancelling the job on your side does not cancel the order; the branch is alerted to arrange another way.
- Full customer contact (name, phone, address) reaches you only for the delivery orders assigned to you.
Endpoints used#
Anything marked “Coming soon” is not served yet; it joins the reference as soon as it ships.
- GET
/partner/v1/ordersNew orders, by cursororders:readAvailable - GET
/partner/v1/orders/{id}One order and its statusorders:readAvailable - POST
/partner/v1/orders/{id}/statusReport a statusorders:statusAvailable - POST
/partner/v1/orders/{id}/eventsRecord a fact on the orderorders:eventsAvailable - GET
/partner/v1/orders/{id}/paymentsPayment, collection and refundspayments:readAvailable