Rimo GlobalTransfers API

Rimo Global · Ground Transportation API

Rimo Global Transfers API

Airport and point-to-point ground transfers worldwide through a single JSON API. Search live vehicles and prices, quote a firm rate, book, and cancel with a reliable verify step, for online travel agencies, tour operators and travel management companies.

Coverage
Airport & point-to-point, worldwide
Rates
Net B2B rates
Vehicles
Sedan, SUV, van, bus & more
Security
Bearer token + IP whitelisting

Search

Live vehicle offers for a route and date, each with price, capacity, luggage and cancellation policy.

Options

Required passenger fields (flight number, driver comments) and optional extras such as meet & greet.

Quote & Book

A firm price with a booking token, then a confirmed booking with a voucher reference.

Cancel & verify

Cancel, then confirm the real status with a read-back — no false errors.

Authentication

API access is available to contracted Rimo Global partners. During onboarding we issue your API token, whitelist your servers' static public IP addresses, and give you your base URL. Send the token in the Authorization header of every request.

HTTP headers
POST <base-url>/api/transferservices/TransferList
Authorization: Bearer <your token>
Content-Type: application/json
Accept: application/json

Credential security

Your token can create real bookings against your account. Store it on your servers only, never in a website or mobile app. If you suspect exposure, contact api@rimoglobal.com and we will rotate it.

Booking flow

Every transfer booking follows the same sequence. Each response carries the keys the next call needs.

  1. 1SearchVehicle offers + pricessearchKey · uniqueKey
  2. 2OptionsRequired fields + extrasper vehicle
  3. 3QuoteCart + price checkbookingToken
  4. 4BookCreates the bookingreferenceNo
  5. 5VerifyRead back the bookingalways

To cancel: Cancellation detail → CancelBooking → read BookingDetails again; the cancel is done only when the status shows Cancelled.

Rules for every request

  • POST with a JSON body (except the two read calls, which are GET).
  • Use keys fresh. searchKey and uniqueKey are short-lived; always search again before quoting and booking.
  • Prices are the total for the transfer in your account currency.
  • Refundable fares are recommended for resale; always read the cancellation policy returned at quote.
  • Errors come back with a status and a message. Check every response, even on HTTP 200.
  • Never retry Book blindly after a timeout — read the booking back with its reference instead (see Cancel & verify for the same principle).

Booking flow

2 · Options

Before quoting, read the per-vehicle passenger fields, available extras and cancellation windows for a uniqueKey.

POST/api/transferservices/IndexingInfo

Required and optional passenger fields (for example Flight Number, Driver Comments). Fill every required field in the quote.

POST/api/transferservices/AncillaryService

Available extras for the vehicle (for example Meet & Greet, usually free). Add the ones your customer chooses to the quote.

POST/api/transferservices/TransferCancellationPolicy

The cancellation windows and charges for the vehicle on the travel date.

Request body (each call)
{ "uniqueKey": "<from search>", "lang": "en" }

Booking flow

3 · Quote

Carry the offer, lead passenger, required fields and extras to a firm price and a bookingToken. Three calls:

POST/api/ShoppingCart/AddTransferToCart
POST/api/ShoppingCart/GetCartDetails
POST/api/ShoppingCart/PriceCheck

PriceCheck response (shape)

Response
{
  "result": {
    "bookingToken": "…",
    "sellingPrice": 12.12,
    "cancellationPolicy": [ … ],
    "priceHike": false
  }
}

Price change

If priceHike is true, the price changed since the search. Show the new price to your customer and get their agreement before you book.

Booking flow

4 · Book

POST/api/Booking/BookService

Books against your credit limit and creates a real supplier booking; the confirmation and voucher are issued. Use the bookingToken from the quote. Send a real lead passenger name in Latin letters.

Response (shape)

Response
{
  "result": {
    "code": 1,
    "referenceNo": "<base64 reference>",
    "bookingId": 431, "detailId": 443,
    "bookingStatus": "Vouchered",
    "supplierConfirmationNo": "69214771"
  }
}

Store the reference

  • Keep the referenceNo. After a timeout never send Book again — read the booking back with the reference (below). The booking may already exist.

After booking

Read a booking

GET/api/Booking/BookingDetails/{referenceNo}

Returns the current status, supplier confirmation, amount, pickup / drop-off and cancellation policy. Use it after every Book, and whenever you need the live status.

After booking

Cancel & verify

Cancellation is two calls plus a mandatory read-back.

POST/api/Booking/BookingCancellationDetail

Preview the refund before cancelling (booking amount, charge, refund).

POST/api/Booking/CancelBooking

Sends the cancellation.

Important — always verify the cancellation

CancelBooking can answer HTTP 400 with INTERNAL_ERROR even when the cancellation succeeded. This is a known behaviour — do not treat it as a failure.

The cancellation is confirmed only when you read the booking back and the status is Cancelled:

Verify step
GET /api/Booking/BookingDetails/{referenceNo}
→ bookingStatus == "Cancelled"   // this, not the CancelBooking HTTP code, is the proof

If it is not Cancelled yet, wait about 10 seconds and read it again. The same verify step is built into the Postman collection (step 9) so you can test it end to end.

Postman collection

The full flow as a ready-to-run Postman collection — search, options, quote, book, read, and cancel with the verify step. Set your base URL and token as collection variables.

Download the Postman collection

Token / cookie

  • Use token (Bearer) authentication only. Cookie / browser-session auth is not supported.

Certification checklist

Tick these before go-live. Your ticks are saved in this browser only.

0 of 0 done

Access
Search & quote
Book
Cancel

Your ticks are saved in this browser only.

Partner support

Questions, a token, or a base URL: api@rimoglobal.com. For the hotels API, see the Rimo Global Hotels API.