Resources · API reference
The LiteHQ REST API
Typed, idempotent, paginated. Everything in the product is one HTTP call away.
Conventions
Predictable shapes. No surprises.
- Cursor pagination
Every list endpoint returns a stable cursor. No offset drift on busy tenants.
- Idempotency keys
Every POST accepts an `Idempotency-Key` header. Replays return the cached response.
- Typed errors
Errors include `code`, `message`, and a docs URL. No HTML pages.
Bookings
Bookings
Create, modify, and inspect bookings across every resource on the floor.
/v1/bookingsList bookings — filter by resource, member, date range, status.
Try it/v1/bookingsCreate a booking. Pricing computed server-side; idempotent on the supplied key.
Try it/v1/bookings/:idReschedule or update billing mode. Conflicts return 409 with the offending booking id.
Try it/v1/bookings/:idCancel a booking. Honors the cancellation window and refund policy on the rate card.
Try it
Members
Members
Member CRUD, tier assignments, and badge/door provisioning hooks.
Companies
Companies
Tenant companies — billing entities that group members and own bookings.
Billing
Billing
Invoices, token transactions, and Stripe Connect proxies.
Visitors
Visitors
Guest invitations, badge-ins, and on-arrival workflows.
Webhooks
Webhooks
Subscribe to events. Signed payloads, automatic retries with exponential backoff.
Auth
Auth
API keys, scoped tokens, and SSO management.
SDKs
Generated from this spec, type-safe on day one.
Build on the same API the app uses.
No private endpoints. Every action in the calendar is a typed REST call you can make yourself.