Lumo polls your catalogue
Expose one endpoint that returns the vehicles you are offering. Lumo reads it on a schedule and mirrors what it finds.
For rental fleets and operators
Keep your own system as the source of truth. Lumo reads your vehicles, lists them to renters across India, and sends bookings back to you — through one published contract you implement once.
Your price is not a share of the renter’s. Lumo’s margin is added on top of it.
What you earn
Lumo does not take a cut of your price. It adds its own margin on top of it and charges the renter the total. Nothing is deducted from what you quoted, so the number you set is the number that reaches your account.
How you connect
Lumo publishes the contract and you implement it — there is no per-partner field mapping to agree, and no bespoke integration to maintain on either side. Start with the first mode and add the others when you need them.
Expose one endpoint that returns the vehicles you are offering. Lumo reads it on a schedule and mirrors what it finds.
Send up to 1,000 vehicles in one request after a bulk update on your side. Retry safely with an idempotency key.
For what cannot wait a sync — a vehicle off the road, a price correction, an insurance lapse. HMAC-signed, replay-protected.
Cancellations, refunds and blocks arrive at your endpoint. Nothing counts as done until your system acknowledges it.
Safeguards
Same rules, same errors, same responses — and nothing you upload there can ever reach a renter. Rehearse the real thing without risk.
If three records in a thousand are malformed, the other 997 go live and the three are held, named by position and field so you know exactly what to fix.
If your API has a bad deploy and returns nothing, Lumo keeps your listings and waits. Your catalogue is only unpublished after you say so twice.
Apply, get your sandbox credentials and the full contract, and validate your feed against the real rules before a single vehicle is visible to a renter.