Operating guide
Four connectivity lanes for different teams
RNR describes connectivity as a choice between an integration and an operating workflow. Buyers can connect to the standard RNR REST API, ask RNR's in-house team to build to the buyer's standard API, use a partner portal, or discuss a DMC model for accommodation plus local services.
Hotels sit on the supply side of the same system: their availability, rates, inventory, and restrictions arrive through an existing channel manager or another agreed loading path. Keeping those two sides distinct makes ownership easier to troubleshoot.
- Standard buyer API: connect your system to RNR's documented booking lifecycle.
- Buyer API build: RNR engineers map and certify a connection to your standard.
- Portal: use a controlled interface when a full integration is not the right first step.
- DMC workflow: coordinate accommodation with ground handling through one local counterpart.
What the hotel API lifecycle covers
The public technical model is a predictable REST lifecycle: search live availability, book, cancel where the agreed rules allow it, and retrieve the reservation. JSON responses carry the booking data, while real-time ARI keeps the search surface connected to source inventory.
Instant confirmation applies when the requested inventory is live and confirmable. Exceptions move into the agreed operations path rather than being hidden behind a generic success response. The full endpoint reference, authentication details, and sandbox are shared under NDA after the integrations team reviews the request.
Questions to answer before technical work
A short technical discovery prevents an API project from becoming a vague feed connection. Bring the systems, booking states, cancellation rules, property and room identifiers, rate requirements, and operational contacts that will define the launch boundary.
- Which endpoints and booking states does your current stack require?
- How will property, room, board, occupancy, and cancellation data be mapped?
- Which authentication, IP, environment, and logging controls are required?
- Who receives booking exceptions and guest-issue escalations?
- What test cases must pass before production traffic is enabled?
A controlled path to API access
Request access with your company, role, distribution model, and preferred connectivity lane. RNR's integration team uses that context to confirm the commercial route, share the appropriate documentation under NDA, agree the mapping scope, and define certification before go-live.
This page is a capability overview, not a substitute for the buyer-specific API contract. Availability, commercial terms, credentials, and implementation timing are confirmed for the connection being proposed.