Register on the Sabre Developer Hub and obtain credentials; car rental SOAP APIs require a Sabre PCC (Pseudo City Code) and a configured agency context
Call the Car Locations API to search for rental locations using airport code or geographic coordinates; the response returns location codes required for availability queries
Call the Car Availability API with pickup and dropoff location codes, dates, and ACRISS vehicle category filter to retrieve rate quotes from connected rental vendors
Review the rate details, insurance options, and included mileage terms in the availability response; surface these clearly to the traveler before confirmation
Call the Car Reservation API (VehRes) with the selected rate key, driver details, and any additional driver or equipment options to create a confirmed reservation
Capture the confirmation number from the response and store it alongside the PNR if part of a multi-segment GDS booking; use the cancel API within the vendor's free-cancel window if needed
Known gotchas
Sabre car APIs are predominantly SOAP-based with XML messaging; expect XML namespace handling complexity and ensure your HTTP client correctly sets the Content-Type to text/xml
Rate keys returned in availability responses are session-scoped and short-lived; the reservation call must occur in the same session context or the rate key will be rejected
Insurance and coverage options vary by vendor and country; some markets require mandatory local insurance add-ons that are not optional in the rate, and failing to include them breaks the reservation call
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp