Quickstart
Five minutes from key to first booking-ready response.
1. Smoke-test your key
curl -u 'dk_live_xxxxxxxxxxxxxxxxxxxxxxxx:' \
https://partner-api.elivaas.com/api/ping
Expect 200 with partnerId echoed back.
2. List the catalog
curl -u 'dk_live_xxxxxxxxxxxxxxxxxxxxxxxx:' \
'https://partner-api.elivaas.com/api/listings?page=1&size=20'
Each row carries the full listing (title, city, status, lat/long, base price) plus a
properties[] array. Every property includes photos and amenities as JSON arrays.
3. Check availability
Inventory is per-property, per-day.
curl -u 'dk_live_xxxxxxxxxxxxxxxxxxxxxxxx:' \
'https://partner-api.elivaas.com/api/inventories?listingIds=lst_0853ie&from=2026-06-01&to=2026-06-15'
You can also pass propertyIds=prop_a,prop_b directly. Default window is today → today+90 days.
4. Read rates
Rates are occupancy-based: one row per (property, date, mealPlan, adults). The
channelId is resolved from your API key — you don't pass it.
curl -u 'dk_live_xxxxxxxxxxxxxxxxxxxxxxxx:' \
'https://partner-api.elivaas.com/api/rates?propertyIds=prop_xyz&from=2026-06-01&to=2026-06-15'
Response sample:
[
{"propertyId":"prop_xyz","date":"2026-06-01","mealPlan":"EP","adults":1,"rate":90000},
{"propertyId":"prop_xyz","date":"2026-06-01","mealPlan":"EP","adults":2,"rate":90000},
{"propertyId":"prop_xyz","date":"2026-06-01","mealPlan":"CP","adults":1,"rate":92373},
...
]
Rates are in the smallest currency unit (e.g. paise for INR).
What's next
- Full schema for each endpoint → API Reference
- Error semantics → Errors