Getting started

Roave API

Search, price and book hotels, flights, activities and transfers from your own systems — the same inventory and agency rates your advisors see in the Roave portal.

What you can build

  • Your own booking engine. Put Roave hotels and travel products behind your agency's website or client app, with your branding and your markup.
  • Mid-office automation. Create bookings from your CRM or itinerary tool and pull confirmations, vouchers and cancellation terms back into it.
  • Reporting. List every booking your agency has made, with its status and earnings, for reconciliation.

How a booking works

Every product follows the same five calls. The guides walk through each one in detail.

  1. SearchPOST /search returns a searchId.
  2. Read resultsGET /search/:id/results lists priced options.
  3. Price-checkPOST /quotes/:id/price-check confirms the live price and terms.
  4. BookPOST /bookings books it, paying from your agency credit with paymentMethod: "credit".
  5. ConfirmGET /bookings/:id returns the confirmation; GET /bookings/:id/voucher returns the voucher.

Products

ProductWhat you can doGuide
HotelsSearch by city, area, point on a map or a single hotel. Net or commissionable rates, room-level rate sheets, holds on refundable rates, cancellation.Quickstart
FlightsOne-way, return and multi-city (up to six legs) in four cabin classes. Booking and cancellation.Flights
ActivitiesTours, tickets and experiences by destination and date. Official supplier vouchers returned with the booking.Activities
TransfersPrivate and shared transfers between airports, hotels and addresses. One-way or return.Transfers

What is on sale can differ by market. Ask the API before you show a product:

Request · cURL
curl "https://api.roaveagents.com/api/v1/search/capabilities?market=GB" \
  -H "X-API-Key: $ROAVE_API_KEY"
Response · 200
{
  "data": { "productTypes": ["hotel", "flight", "activity", "transfer"] },
  "meta": {},
  "error": null
}

Before you start

  1. A Roave agency account. Request access if your agency doesn't have one yet.
  2. A signed distribution agreement. An agency admin signs it once in the portal. Until it is signed, price-checks and bookings can be refused with 403 agreement_unsigned.
  3. An API key. An agency admin creates one in the portal under Team → Integrations, in the API keys card. See Authentication.
  4. A server. The API is for server-to-server calls only. It doesn't send CORS headers, so browser code can't call it — keep your key on your backend.

Base URL

All endpoints live under one versioned base URL, over HTTPS only:

Production
https://api.roaveagents.com/api/v1

Where next