Platform Architecture
The Allbookers ecosystem has three distinct components. Understanding how they interact is the foundation for a successful integration.
The Three Components
Every Allbookers integration involves exactly three parties communicating with each other:
Allbookers Panel
panel.allbookers.com
Hotel owners manage properties, rooms, rate plans, availability, and photos.
Allbookers Backend API
allbookers.com
Serves live property data to affiliates. Your integration communicates with this directly.
Affiliate Site
e.g. hotelschecking.com
Calls the Allbookers API to display properties and prices. Maintains a local database.
| Component | URL | Description |
|---|---|---|
| Allbookers Panel | panel.allbookers.com |
Hotel owners manage property profiles, rooms, rate plans, availability, and photos. |
| Allbookers Backend API | allbookers.com |
Serves live property data to affiliates. This is the system your affiliate communicates with directly. |
| Affiliate Site | e.g. hotelschecking.com |
Calls the Allbookers API to display properties and prices. Maintains a local database with enrichment data. |
What Allbookers Controls
The following data is owned and maintained by Allbookers. Your affiliate reads this data but never writes to it:
- Hotel owner accounts
- Room types, rate plans, availability, and nightly pricing
- Cancellation and refund policies
- Meal plans
- Room and property photos (served from allbookers.com)
- Reviews collected via the Allbookers platform
What the Affiliate Manages Locally
Your affiliate maintains its own database with supplementary data not provided by the API:
- Star ratings and property type
- Full address (city, street, country)
- Primary listing photo
- Points of interest and distances
- Guest reviews collected by the affiliate
- End-user accounts and wishlists
Merging at query time
Before rendering any property, your code merges live API data with local records using propertyId as the join key. See Data Enrichment for details.