Partner dispatch API
Trigger a nearby two-wheeler when an order fires from POS, aggregator, or custom pipeline. Fare estimate before accept; live status after assign.
B2B · India
Fleet-as-a-Service for last-mile partners
Programmable 19Cabs fleet for food delivery pipelines, POS systems, and logistics aggregators — API dispatch, nearby two-wheeler riders, OTP proof of delivery, prepaid partner wallet.
Share city, daily trip volume, and average distance — we reply with integration path and a draft rate card.
Offerings
What Fleet-as-a-Service includes
Built for partners who need developer-friendly last-mile — not a white-label consumer brand swap.
OTP proof of delivery
Drop OTP confirms the trip complete. That event drives partner billing and rider earnings credit — no “he said / she said” completion.
Prepaid partner wallet
Top up by UPI or NEFT. Per completed delivery deduction on a published base + km formula. Optional weekly invoice for limited pilots.
Food, parcel, logistics
Restaurant last-mile, door-to-door parcels, and B2B aggregators who need programmable transportation without taking a food commission cut.
Integration
How a partner books a delivery
Clear path from order event to OTP-complete settlement.
-
Order event Your POS or pipeline creates a delivery job (pickup kitchen / hub, drop customer, notes).
-
API create trip Call 19Cabs with pickup, drop, and vehicle preference (typically two-wheeler for food last-mile).
-
Nearby rider assigned Matching uses the same live driver network as the consumer apps — bike / auto / car where relevant.
-
OTP complete → settle Customer OTP confirms delivery. Partner wallet deducts the delivery fee; rider gets in-app earnings credit.
Commercials & coverage
Pricing and cities — honest defaults
Volume slabs, last-mile only
- Base + per-km delivery fee with volume slabs (example pilots up to ~100 trips/day).
- No food commission — restaurant order value stays with the restaurant / aggregator.
- Prepaid wallet preferred; weekly invoice for short pilots.
- Rate card after we know city, daily volume, and average km.
India coverage, supply-first
- City landing pages cover 703 markets — see cities.
- Two-wheeler density is strongest in core markets (Kanpur and nearby UP).
- New-city B2B pilots need a committed daily volume so we can build supply with you.
- We do not claim city-wide SLA until supply is live for that partner corridor.
FAQ — Fleet-as-a-Service
What is 19Cabs Fleet-as-a-Service?
Fleet-as-a-Service is 19Cabs’ B2B offering for partners who need programmable last-mile dispatch — food delivery pipelines, POS integrations, and logistics aggregators. Partners call an API to create a trip; 19Cabs assigns a nearby two-wheeler rider from the same driver network used by the consumer apps.
How does API integration work for food delivery or POS?
Typical flow: order event from your POS or pipeline → API create trip (pickup, drop, vehicle preference) → nearby two-wheeler assignment → live status → drop OTP confirms delivery complete → partner wallet is billed for the delivery fee. Start with a technical call, then pilot keys.
How is Fleet-as-a-Service priced?
Partners pay a volume-based delivery fee (base + distance slabs), usually via a prepaid partner wallet topped up by UPI or NEFT. 19Cabs charges last-mile only — not a food commission on restaurant order value. Exact rate cards depend on daily volume and average trip distance.
Where is Fleet-as-a-Service available in India?
19Cabs city pages cover 703 markets across India. Two-wheeler supply density is strongest in core cities such as Kanpur and nearby UP markets. New-city B2B pilots are discussed against a committed daily volume so supply can be built with the partner.
How do I start a partnership?
Email nineteencabs@gmail.com with city, expected daily trips, average distance, and integration type. For AI agent booking on the same network, see Agent Console and Book with AI.