Kilo Docs

Docs / Get started/ Introduction

Introduction

Updated Aug 9, 2026

The Kilo Business Delivery API lets your server create and manage fleet deliveries the same way the public request form does.

Who this is for

  • You run a business on Kilo.
  • You have (or are building) a WhatsApp / AI bot that talks to customers.
  • Your bot's backend will call Kilo with an API key.

Who this is NOT for

  • Do not put your API key in a browser, mobile app, or WhatsApp client.
  • Do not call Kilo directly from a customer's phone.

What you can do

  1. Discover what the business offers (services, warehouses, service locations, payments).
  2. Create a delivery (pickup, dropoff, package photos, payment method).
  3. Get one delivery by id.
  4. List deliveries.
  5. Cancel a delivery when the rules allow it.
  6. Receive webhooks when something changes (created, cancelled, completed, …).
  7. Optionally turn off Kilo's customer SMS / WhatsApp / email and send those yourself from webhook events.

Own your customer notifications

If your bot already talks to customers (WhatsApp, SMS, in-app):

  1. Dashboard → Settings → Notifications.
  2. Turn Customer delivery messages off.
  3. Keep webhooks on (Settings → API & Webhooks) and send status updates from your side.

Kilo still runs the delivery. OTPs and rider ops messages are unchanged — only customer-facing status / tracking / feedback messages stop.

Mental model (read this twice)

Think of three boxes:

  1. Your bot — talks to the human in natural language.
  2. Your backend — turns that chat into a clean JSON body + downloads/hosts package images.
  3. Kilo — creates the delivery for your fleet, applying your coverage, pricing, and settings.

Kilo does not parse the WhatsApp text for you. Your backend must send complete data.

Next step

Prefer building with an AI coding agent? Start at Build with AI — copy a ready-made implementation prompt (WhatsApp bot, store fulfillment) that includes the API reference and a human setup checklist.

Otherwise start with Capabilities & locations (how the public form chooses services), then Authentication. For exact JSON success/error shapes and field types, see API reference.

Capabilities & locations →