Back to documentation

OTA integration

OTA partner channel integration

How brokers connect to Rentlica over OpenTravel XML — endpoints, credentials, message types, and the dashboard setup flow.

Rentlica acts as the supplier server for car hire brokers. Each partner channel gets a unique endpoint URL, RequestorID, password, and optional IP allowlist. Brokers search your mapped locations, pull live availability and rates, and push reservations that land in the same booking pipeline as desk and website sales.

Overview

OTA partner channels let rent-a-car companies sell through major brokers without maintaining a separate inventory system. Rentlica exposes a single XML endpoint per channel. When a broker sends a VehAvailRate request, Rentlica answers from your live fleet, mapped locations, and pricing rules. Reservations created via VehRes appear in the dashboard with the broker as the booking source.

How it works

  • You connect a broker profile in Integrations → Partner channels and receive credentials.
  • You map Rentlica branches to OTA location codes and fleet categories to ACRISS codes.
  • The broker points their integration at your endpoint URL and allowlisted IPs.
  • Inbound XML messages are authenticated, logged (PII-redacted), and handled idempotently.
  • Bookings sync into the same availability engine that powers your desk and REST API.

Endpoint

Brokers POST OpenTravel XML to your channel-specific URL. SOAP-wrapped bodies are supported when the broker profile requires it. GET requests return a helpful error — brokers must use POST.

Authentication

  • Endpoint key in the URL must match the channel created in the dashboard.
  • RequestorID in the XML POS block must match the channel credentials.
  • Password is verified against the stored hash — share it with the broker once, then rotate if needed.
  • Source IP must appear in the channel allowlist when IPs are configured.
  • A RequestorID that does not match the endpoint key is rejected — no cross-tenant routing.

Message types

CodeMessage
VEH_LOC_SEARCHLocation search
VEH_AVAIL_RATEAvailability & rates
VEH_RESReservation
VEH_MODIFYModify
VEH_CANCELCancel
VEH_RET_RESRetrieve

Dashboard setup

  1. Open Integrations → Partner channels and click Connect partner.
  2. Choose the broker profile (Rentalcars, CarTrawler, etc.) and create test or live credentials.
  3. Copy the endpoint URL, RequestorID, and password for the broker's technical team.
  4. Map locations — link each Rentlica branch to the OTA location code the broker expects.
  5. Map vehicle classes — assign ACRISS codes to your fleet categories.
  6. Run the built-in connection test to verify location search, availability, and a sandbox booking.
  7. Switch to live and share your allowlisted broker IPs when certification is complete.

Supported brokers

Rentlica ships broker profiles for Rentalcars / Booking.com, CarTrawler, Discover Cars, Auto Europe, Carnect, and other major marketplaces. Each profile knows how the broker formats credentials (ID + MessagePassword vs Carnect-style attributes) and whether SOAP wrapping is preferred.

OTA vs REST API

Partner channels use OpenTravel XML for broker integrations. The Rentlica REST API and webhooks are separate — use them for your website, CRM, or custom tools. Many operators run both: XML for OTAs and REST for everything else.

Technical reference

The interactive API docs include an OTA Partner Channels section with endpoint details, authentication rules, and the full message-type matrix.

Open OTA section in API docs

Common questions

No. Rentlica is the supplier server. Brokers connect directly to your endpoint once locations and classes are mapped.

Ready to modernise your car rental operation?

Start your 7-day free trial of Rentlica — rent-a-car software with no credit card, no setup fees, and no surprises.