Integrations
What Holidario Channel Manager manages for you
Understand what you configure in Holidario and why you do not need another provider's access or credentials.
- I manage my own rentals
- I own or administer an agency
- I manage operations
- Owner
- Agency
On this page
Holidario Channel Manager is the product's integrated distribution layer. In normal use, your team works inside Holidario and does not need to sign in to an external tool, purchase another account, or enter an API key.
What your team configures#
- Agency Define business data Create property and operation; confirm listing, ID, URL, prices, availability, and cutover from another PMS.
- Holidario Manage technical infrastructure Create or verify elements, transmit changes, and receive compatible bookings/messages with team separation.
- OTA Retain account controls Ownership, authentication, and listing decisions still require agency validation where applicable.
- Review Check before activation A new connection remains inactive until mapping, prices, availability, and writer system are reconciled.
Inside Holidario, an administrator:
- creates the property and its rental operation;
- records the name, identifier, and URL of each OTA listing;
- defines prices, minimum stays, and availability;
- prepares infrastructure for each rental;
- reviews the calendar before activation;
- connects each listing from its operation page.
These are the business details your agency must decide.
What Holidario manages#
Holidario uses its managed connection to create or verify the required technical records, send changes, and receive supported bookings and messages. A person who manages the team can also use Pull future reservations on the Operations list to request Booking.com and Airbnb bookings without accessing the provider tool. Each team is separated within that integration.
When a received reservation creates an internal alert, Holidario applies the recipient roles' arrival-date limits and that person's preferences. The technical provider does not replace these team rules. Provider-level email is handled by Holidario and is not sent to your agency's office, owner, or team-member addresses.
Your team should not:
- request an API key from the technical provider;
- share Holidario credentials with a third party;
- configure internal identifiers manually;
- attempt to repair synchronization from an external provider account.
Where work happens#
- Operations: request future Booking.com and Airbnb reservations in bulk for selected short-term rental operations.
- Operation > Connected Channels: record listings, connect supported OTAs through Holidario, and see whether each connection is inactive or active.
- Price Calendar: define and assign prices before opening sales.
- Pending Tasks: see the next missing requirement for each operation.
Responsibility boundaries#
Holidario does not decide which listing belongs to a property, which price your agency should sell, or when to cut over from another PMS. Your team must validate those decisions.
Do not interpret connection created as channel active. A new connection is created inactive so you can review it before opening it.
Likewise, import queued confirms that Channex accepted the request, not that every reservation is already reconciled. The pull does not synchronize rates, minimum stays, or availability: review the received reservations first and use calendar synchronization as a separate action when appropriate.
If the service is unavailable#
Do not look for external credentials. Ask for help and include:
- the team and property;
- the screen where the notice appears;
- the exact error text;
- the date and time of the attempt.
Do not include passwords, cookies, verification codes, or API keys.