OTA_GroundBookRQ (Transfer Booking Request) is used to quote or commit a ground transfer reservation, including service details, locations (Pickup/DropOff), passenger data, and partner references.
OTA_GroundBookRQ API call
Skip & Hit the Playground.
Purpose
Use this message to:- Request a quote (price + availability) without creating a booking by setting
ResStatus="Quote". - Commit a definitive booking by setting
ResStatus="Commit".
Structure – Root Element
xmlns: must behttp://www.opentravel.org/OTA/2003/05.Version: recommended2012.2.ResStatus:Quote|Commit.EchoToken: optional but recommended for idempotency and tracing.
Structure – Core Elements
POS (Point of Sale)
Identifies the requesting party and carries credentials.GroundReservations
Holds the service to be quoted or booked: locations, product and pricing qualifiers, and passengers.Specify the service code that has to be booked. e.g S0000, PW000,… VehicleType
Define the returned description in the availability call of the desired product. RateQualifier
PromotionCode defines if the trip is IN, OT, or both. RateQualifier defines the transfer stock code.
Locations
Each requested transfer is expressed with aLocation (reference it by RPH). Provide the appropriate Pickup/DropOff details for each leg.
Flights at airports must include both the arrival and departure airport codes and times in
AirportInfo. Use DateTime in ISO 8601.Passengers
Provide the lead passenger underPrimary and any others under Additional. Age is required (age at time of service).
TPA_Extensions
Partner References
Partner references are mandatory. Use one master reference (Type="36") and one child reference (Type="37") per Location (Item_RPH maps to the Location’s RPH). See Master and child references
Extras
Optional extras returned by availability can be added asFees.
Default Service
IfServiceLevel/RateQualifier are omitted, the system will select the cheapest available option for the specified locations and passengers.
Complete Examples
Playground
OTA_GroundBookRQ API call
Try our API playground in real time.
Best Practices
- Always include
EchoTokento correlate requests and responses. - Use ISO 8601 for all dates/times (
YYYY-MM-DDThh:mm:ss). - Provide both arrival and departure flight legs when an airport is involved.
- Include ages for all passengers; age is evaluated at time of service.
- Send
UniqueID(master + child per leg) to prevent duplicates and enable partial cancellations. - If you don’t have a specific service code, omit
ServiceLevel/RateQualifierto book the cheapest option.

