VillaSlot books villas by the slot. A villa has opening hours and a rate grid; a customer books an hour, a morning or a day; the booking gets confirmed, paid, completed — or cancelled.
That is the whole product, and everything it does is reachable over HTTP.
Your team and your villas. Everything below belongs to exactly one organization, and nothing crosses between two. Your plan limits how many villas, bookings and customers it holds.
A place you rent by the slot. It carries its opening hours — a weekly grid, per day — and its rate grid, which prices a duration. Outside its hours, nothing can be booked.
Whoever books. A name, a way to reach them, and their history. A customer can be given an access link: it connects them to their own space, where they see their bookings and their balance, and nothing else.
A villa, a customer, a slot. It moves through states — pending, confirmed, completed, cancelled — and it can carry a payment.
A booking can be paid in full, partly, or not at all. A payment link goes to the customer; Stripe answers back and the booking follows.
The interface — the calendar, the villa pages, the customer list. Made for the person with the customer on the phone.
The API — the same data, the same rules, no browser. Made for a script, a site, or an agent. An API key belongs to one organization and carries the rights of whoever created it: nothing is possible through the API that the same person could not do by hand.
The API is the interesting half of this documentation. Head to API — it is the map of every endpoint, with a page per call.
1500000 in IDR is 15 000 rupiah.
Never divide by 100 without knowing the currency.409, in the
interface and in the API alike.