Two-Way RMS Cloud Integration for Revenue Management
Propeter integrates with RMS Cloud in both directions. It reads your configuration, inventory, reservations and occupancy, and publishes approved rates back to RMS Cloud. Your team approves every rate before it is sent, and RMS Cloud remains your system of record.
Available
Integration status
Two-way
Direction
RMS Cloud API
Connection
What Moves Between RMS Cloud and Propeter?
Inbound, Propeter syncs your RMS Cloud configuration (properties, room types, rate plans and rates) together with inventory, guests and occupancy on a schedule, and receives reservation and guest updates by webhook. That data drives demand forecasts and rate recommendations. Outbound, rates your team approves are pushed to RMS Cloud through its rate-adjustment API, and direct bookings taken on the Propeter booking engine are created in RMS Cloud at confirmation.
- Read: properties, room types, rate plans, rates, inventory, guests and occupancy
- Received: reservations and guest updates by webhook
- Written: approved rates through the rate-adjustment API, and direct bookings at confirmation
What Stays in RMS Cloud, and What Happens When Something Fails?
RMS Cloud stays your system of record for reservations, folios, housekeeping and the night audit. Propeter only writes rates your team has approved and the direct bookings it takes. Reservation delivery uses durable queues, retries, idempotency keys and a dead-letter queue, so a failed delivery is visible and recoverable rather than silent.
- Rates are only pushed after approval, individually or in bulk
- Floors, ceilings and discount caps apply before any rate can be approved
- Every approval is recorded in an audit log with user attribution
RMS Cloud Integration at a Glance
What connects, what is read and written, and what you need to get started.
Connection
The RMS Cloud API, using API credentials for your property set up with your team during connection.
Propeter reads
Configuration, rates, inventory, guests and occupancy on a schedule; reservations and guests by webhook.
Propeter writes
Approved rates through the RMS Cloud rate-adjustment API, and direct bookings at confirmation.
RMS Cloud keeps
Reservations of record, folios, housekeeping, front office and the night audit.
Failure handling
Durable queues, retries, idempotency keys and a dead-letter queue for reservation delivery.
Mapping
Room types and rate plans are mapped during configuration. How your property types map is confirmed during implementation planning.
Frequently Asked Questions
Running RMS Cloud? See the two-way flow.
Book a demo to see RMS Cloud data in Propeter, rate recommendations with their reasons, and approved rates going back to RMS Cloud.