Bu sayfa henüz çevrilmedi, bu yüzden İngilizce sürümünü okuyorsunuz.
Guests, loyalty and memberships
Guest Memory and consent, the loyalty programme, paid memberships and win-back when rooms are empty. The hotel endpoints and the guest-facing ones.
These endpoints are called with a signed-in person's login (a Firebase ID token), inside their role. The loyalty programme and memberships are one per account (every hotel of a group shares them).
Guest Memory and consent
| Endpoint | Permission | What it does |
|---|---|---|
GET / PUT /api/v1/guests/memory/settings?property_id= | settings.manage to change | On or off, whether guests are asked to confirm, the catalogue of preferences |
GET /api/v1/guests/{guest_id}/memory | any login | Preferences (CONFIRMED or SUGGESTED, with the guest's own words) and consent |
POST /api/v1/guests/{guest_id}/memory | reservations.manage | Add one: key from the catalogue, optional value |
POST /api/v1/guests/{guest_id}/memory/{pref_id}/confirm | reservations.manage | Confirm a suggestion |
DELETE /api/v1/guests/{guest_id}/memory/{pref_id} | reservations.manage | Forget one |
PUT /api/v1/guests/{guest_id}/consent | reservations.manage | The guest's yes or no to offers, per channel |
Nothing about health, religion or anything like it is ever kept. A guest's own page (/public/v1/stay/{token}) lists
what the hotel remembers, and DELETE /public/v1/stay/{token}/memory/{id} forgets it.
Loyalty
| Endpoint | Permission | What it does |
|---|---|---|
GET /api/v1/loyalty | any login | The programme and its numbers |
PUT /api/v1/loyalty | settings.manage | Change it: name, free_night_every, tiers and perks, enabled |
GET /api/v1/loyalty/members?q= | any login | Members, most nights first |
GET /api/v1/loyalty/members/{id} | any login | One member, free nights and history |
POST /api/v1/loyalty/members/{id}/adjust | settings.manage | Add or take nights, with a reason |
POST /api/v1/loyalty/guests/{guest_id}/join | reservations.manage | The guest joins at the desk |
Only direct stays count, once checked out and paid in full. Free nights are gift vouchers spendable at any of the
account's hotels. The booking page takes guest.join_loyalty. A member's card is at /public/v1/card/{token} (JSON),
/public/v1/card/{token}.png, /public/v1/card/{token}/wallet.pkpass (Apple Wallet) and
/public/v1/card/{token}/google (Google Wallet).
Memberships
| Endpoint | Permission | What it does |
|---|---|---|
GET /api/v1/memberships | any login | Plans, memberships, numbers |
POST /api/v1/memberships/plans / PATCH .../plans/{id} | settings.manage | A plan: price, period (MONTH or YEAR), discount_pct, nights_cap, perks |
POST /api/v1/memberships/guests/{guest_id} | reservations.manage | Sell one: by card (a Stripe subscription page) or paid at the desk |
POST /api/v1/memberships/{id}/renew / .../cancel | reservations.manage | Renew at the desk, or end at the end of what was paid |
Each plan has a members' code: on the booking page it applies only to the member's phone or email.
Win-back when rooms are empty
GET and PUT /api/v1/win-back?property_id= (settings.manage): the settings (threshold, days ahead, offer percent,
daily cap, WhatsApp and email), the preview of the next send (nights, guests by channel, offer, Meta's cost, a sample)
and the sends so far. Nothing is sent until the owner's {"approve": true} after the preview. Only guests who agreed
to offers are written to; GET /public/v1/offers/stop is the email's stop link.
Bir şey mi geliştiriyorsunuz?
AI manager
Jobs the AI manager does for a hotel every day inside the owner's limits, the price questions waiting for a yes, what it did and what it earned. Its settings, answering a question, and running it now.
ChatBeds Network
Referrals between hotels when one is full, walks, monthly statements between hotels, shifts for network staff, and good guests' signed records. The hotel endpoints, the booking page's, and checking a signed record yourself.