Your data, over a
clean REST API.
open.rentibly.app/v1 is live: read and write properties, bookings, contacts, quotes, inquiries, tasks, operations, expenses and more — with OAuth, signed webhooks and keys you mint yourself.
curl https://open.rentibly.app/v1/bookings?status=confirmed \
-H "Authorization: Bearer rk_live_••••••••"
{
"data": [
{ "ref": "RTB00317", "property": "RTP00042",
"check_in": "2026-09-12", "check_out": "2026-09-19",
"total": { "amount": 288400, "currency": "USD" } }
],
"has_more": true
}What's live today
Read + write across the platform
Properties, bookings, contacts, quotes, inquiries, tasks, operations, expenses and custom fields — full CRUD where it makes sense, idempotency keys on every write.
Webhooks that behave
Six events — bookings, cancellations, contacts, accepted quotes, completed operations, expenses — signed, retried with backoff, managed from Settings → Developer.
OAuth or API keys
Standards-compliant OAuth with refresh rotation and a consent screen for apps; self-serve scoped keys with a full audit trail for scripts.
Documented like we mean it
A published OpenAPI 3.1 spec
34 paths, 52 operations, CI-gated so the spec can't drift from the code.
Docs inside the product
Per-endpoint parameters, request bodies and response shapes at Settings → Developer — next to the keys that call them.
Zapier, by invite
A private Zapier app — 12 triggers, 11 actions, 3 searches. Ask us for the invite link; directory listing comes later.
What we won't pretend is ready
Accounting integrations
Zoho Books, Xero and QuickBooks are not built. When they are, the integrations page will say live — that's the rule.
Zapier in the public directory
The app works today by invite; the public listing is a separate submission we haven't made yet.
Microsoft & Zoho calendars
Calendar Connect is Google-only for now — the others are designed, not shipped.
Build against real data in the demo.
We'll mint a key against a sandbox tenant and make the first call together.
Book a demo