API

Getting Started

How to approach FullHotel public APIs, stable surface area and integration prerequisites.

Version 1.0.0
Last updated 2026-05-26

Public API baseline

Use FullHotel public APIs for three main flows:

  1. Availability and quoting
  2. Reservation create or update
  3. Public self check-in session handling

Stable perimeter

Document only what is public and stable:

  • /api/v1/booking/*
  • /api/v1/checkin/*
  • selected public webhooks

Internal admin, tenant backoffice, billing, RBAC and authority internals are intentionally excluded.

Rate limits

Public endpoints are protected by throttling. Integrations should:

  1. Retry only on transient failures
  2. Cache availability queries when possible
  3. Avoid burst traffic on identical payloads

Sandbox and rollout

Use a demo tenant or a staged tenant with real plan features enabled before going live.

Next reads