Reservit Basics for Module Users

1. Reservit account structure

A Reservit account is organised in a hierarchy. At the top is the property — the hotel, apartment complex or group of properties you manage. Within the property, Reservit organises accommodation into room types, which are categories of physical rooms that share the same attributes (size, bed configuration, view, amenities). Within each room type, individual rooms are defined by their physical identifier (room number or name) and their inventory count.

Rates in Reservit are managed at the room type level via rate plans. A rate plan is a named pricing structure that defines the base rate, included services and any conditions (breakfast included, non-refundable, minimum stay) for a given room type. Most properties operate multiple rate plans simultaneously — for example, a best available rate plan, a non-refundable advance purchase plan and one or more contracted corporate rate plans.

Above the room type level, Reservit organises rate plans into rate categories — groupings that control which rate plans are published to which channels. Understanding rate categories is essential for channel management: if a rate plan is not assigned to the correct category, it will not be distributed to the OTAs connected through your Reservit channel manager, and no ItReserve module can push rates for it.

Reservations in Reservit are the core transactional records. Each reservation contains: the guest profile, the room type and specific room assigned, the rate plan applied, the stay dates, the folio (the running total of charges), and a status (tentative, confirmed, checked-in, checked-out, cancelled). ItReserve modules — including Yield Manager, Guest Comms and Invoice Module — read reservation data to trigger their operations. The accuracy of your Reservit reservation data therefore directly affects the quality of what ItReserve produces.

2. Key concepts: rate plans, room types and restrictions

Rate plans are the pricing engine of your Reservit account. Each rate plan has a base rate (either a flat amount or a percentage derived from another rate plan) and a set of applicable dates. Rate plans can be seasonal — defined for a specific date range — or open-ended with manual override rates for key dates. When Yield Manager pushes an updated rate, it writes to the rate plan record for the specified room type and date range via the Reservit API. Understanding the name and ID of each rate plan in your account is therefore a prerequisite for configuring Yield Manager rules correctly.

Room types define the sellable unit. A room type in Reservit must have at least one rate plan attached before it can be distributed through any connected channel. Room types also carry availability — the count of rooms of that type available to sell on any given date. ItReserve Channel Bridge reads and writes availability at the room-type level. When a reservation is made on a niche OTA connected via Channel Bridge, availability is decremented in Reservit automatically and the reservation is created in Reservit's booking list.

Restrictions are conditions applied to specific dates or date ranges that modify how a rate plan is sold. The most commonly used Reservit restrictions are: closed to arrival (CTA — the property will not accept new arrivals on this date), closed to departure (CTD — guests may not check out on this date), minimum length of stay (minLOS — guests must book at least N nights), and stop sell (the date is closed to all new bookings, regardless of rate plan). Restrictions are typically set in Reservit's Restrictions or Rate Management screen and propagate through the channel manager to connected OTAs. Channel Bridge extends this propagation to niche channels that Reservit's native channel manager does not reach.

3. Navigating the Reservit dashboard

The Reservit dashboard is divided into several primary sections, typically accessible from the left-hand navigation menu. The sections most relevant to ItReserve module users are:

• Reservations — the booking list and individual reservation record view. ItReserve Guest Comms and Invoice Module read from this section.
• Rooms / Room Types — your property's room inventory and type definitions. Channel Bridge reads room type IDs and availability from here.
• Rates — rate plan management, where base rates, seasonal rates and restrictions are configured. Yield Manager writes updated rates to this section.
• Channels — the native Reservit channel manager, showing connected OTAs and distribution settings. Channel Bridge augments this section with additional channels not in Reservit's standard list.
• Reports — Reservit's built-in reporting suite. Analytics Board reads the underlying data that powers these reports and exposes it in a custom dashboard format.
• Settings > Integrations or Settings > API — the section where your Reservit API key is found. This is the credential you enter into the ItReserve dashboard to connect your first module.

The exact menu labels and layout can vary slightly between Reservit account tiers and regional configurations. If you cannot find the Integrations or API section in your Reservit account, contact Reservit support to confirm that API access is enabled for your subscription tier.

4. Understanding the Reservit API

The Reservit API is the programmatic interface through which ItReserve modules communicate with your Reservit account. It is a REST API that accepts and returns JSON. Authentication uses an API key — a long string of characters that acts as a credential identifying your Reservit account.

The API is organised into resources corresponding to the main objects in your Reservit account: properties, room types, rate plans, restrictions, reservations, guests and folios. Each ItReserve module uses a specific subset of these resources. Yield Manager uses rate plans and availability. Channel Bridge uses availability, restrictions and reservations. Invoice Module uses reservations and folios. The exact API scopes each module requests are documented on the module's catalogue page.

Reservit issues API keys at the account level. A single key can be used by all ItReserve modules simultaneously — you do not need separate credentials per module. However, if your Reservit account is configured with multiple properties, confirm with Reservit whether your API key provides access to all properties or only the primary property in the account hierarchy.

The Reservit API has rate limits — a maximum number of requests per minute and per day. ItReserve modules are designed to stay within standard Reservit API rate limits. If you are using multiple ItReserve modules simultaneously alongside other Reservit integrations, monitor your API usage from the Reservit developer section to ensure you are not approaching the limit for your tier.

5. How ItReserve modules interact with Reservit data

Every ItReserve module operates as a read-extension or a read-write extension of your Reservit account. Read-only modules — such as Analytics Board and Reputation Manager — retrieve data from your Reservit account and present it in a different format or context. They do not change any data in Reservit. Read-write modules — such as Yield Manager, Channel Bridge and Guest Comms — both read Reservit data and write back updates: rate changes, availability adjustments, new reservation records.

When you connect a module by entering your Reservit API key in the ItReserve dashboard, the module requests only the scopes it needs. For example, Yield Manager requests read access to reservations and rate plans, and write access to rate plans. It does not request access to guest profiles or folios. This scope separation limits the blast radius of any configuration issue to the areas the module actually touches.

ItReserve modules poll the Reservit API on a defined schedule — typically every 5 minutes for availability and reservation updates, and within 60 seconds of a user-triggered action in the ItReserve dashboard. If you make a change directly in your Reservit account that affects a module's operation (for example, adding a new room type or changing a rate plan ID), allow up to 5 minutes for the module to detect the change automatically, or use the "Sync now" button in the module settings to trigger an immediate refresh.