Let's Pizza Developersv1.0.0

Guides

Delivery fleets

The kitchen owns the order up to ready; the fleet owns it after. Let’s Pizza joins the two.

The flow#

  1. Branch → Let's PizzaOrder ready
  2. Let's Pizza → Your systemA delivery joborder.ready
  3. Your system → Let's PizzaThe rider has the foodstatus: out_for_delivery
  4. Your system → Let's PizzaDelivered (or failed, with a reason)status: delivered
  5. Your system → Let's PizzaCash collected at the doorPOST …/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.