HiLucy is built API-first: every screen in our production guest and staff apps runs on the same authenticated REST API we open to partners, so nothing you integrate against is a bolt-on. Sandbox access is granted on request — a dedicated, isolated environment with seeded demo data and individually revocable credentials, free while you build. When your integration is validated in sandbox, production access is enabled per-agreement.
Sandbox access is provisioned per partner, on request. Here is what's in it.
The sandbox is isolated infrastructure with its own database — nothing it touches is production.
Representative reservations, folios, and menus come pre-loaded, so you can exercise real flows — bookings, charges, orders — from your first request.
Payments run against Stripe test keys. You can take a booking through checkout end to end with no real card and no real money.
Credentials are issued individually, scoped to your sandbox property, and can be rotated or revoked without touching anyone else's access.
You get a named person on our team while you integrate — not a ticket queue.
Sandbox access costs nothing during the program. Commercial terms only enter the picture with production access.
Every integration page publishes a scope table stating direction, what triggers each sync, and what is not synced — per object. The three partners ask about most:
Read-only. We read reservations, guests, and rooms every 15 minutes and never write back — the PMS stays the system of record for the booking, which is the safe default for an integration sitting next to your revenue.
View scope tableTwo-way. In-chat charges and card-on-file holds go out; payment results come back on webhooks. In sandbox, all of it runs in Stripe test mode.
View scope tableTwo-way messaging on the official WhatsApp Business API: inbound guest messages, replies, and Meta-approved templates outside the 24-hour window.
View scope tableWe would rather you find these edges here than three weeks into a build.
There is no signup form and no developer portal. Credentials are issued per partner, by a person, when sandbox access is granted.
The API evolves with the product. We do not yet publish frozen versions or a deprecation policy — build in sandbox first and validate before anything touches production.
We do not publish uptime numbers or support response guarantees yet. What we offer is a named contact and straight answers.
Production API access is not self-serve: it is enabled per-agreement, after your integration is validated in sandbox.
Tell us what you're building and we'll set you up. Sandbox is free while you build; production access follows per-agreement once your integration is validated.
Email [email protected]