Sabre GDS API Configuration
The Sabre GDS API Configuration & Setup process links your Sabre account with QuoteCloud, allowing you to automatically import booking data and generate professional travel itineraries. This guide explains the setup steps to complete the integration.
Configure Sabre GDS in QuoteCloud
Connect your Sabre GDS account to a QuoteCloud team.
Configure itinerary templates and automated Sabre itinerary placeholders.
Set up Sabre GDS itinerary integration
Open QuoteCloud Settings
From the Dashboard, open the user menu and click Settings . This opens the administration and configuration area for your QuoteCloud account.Open the Teams section
Under Users & Roles , click Teams . Each team can maintain separate travel API and itinerary integration settings.Select the team to configure
Locate the team you want to connect with Sabre GDS and click Edit . This opens the team configuration settings window.Open Travel API Settings
Inside the team settings window, select Travel API Settings . This section controls integrations between QuoteCloud and external travel systems.Configure the Sabre connection type
Under the Sabre GDS tab, set the connection type to: Authenticate via Downline API OrderSelect the itinerary template
Choose the itinerary template that should be used for Sabre-generated itineraries. The selected template should contain an Itinerary Placeholder where Sabre booking data will automatically populate.Enter your Sabre credentials
Complete the required Sabre connection details including: Queue Number Domain PCC User ID PasswordSave the Sabre configuration
After entering all required credentials, click the green Save button. QuoteCloud will now store and activate the Sabre GDS integration settings for the selected team.Verify the itinerary template
After saving, open the itinerary template selected earlier. This allows you to confirm that the template is configured correctly for automated Sabre itinerary population.Review itinerary placeholders
Inside the template, itinerary blocks will display placeholder sections showing where Sabre itinerary data will automatically appear. These placeholders are dynamically replaced with live booking information during itinerary generation.Configure pricing table placeholders
Pricing Tables can also function as itinerary/API placeholders for automated pricing information. Right-click the Pricing Table and open Pricing Table Settings .Enable API placeholder mode
In the settings panel, enable Set as itinerary/API placeholder . Once enabled, the Pricing Table will display a placeholder badge showing it is linked to Sabre GDS automated data.
FAQs
What is the Sabre GDS API Configuration in QuoteCloud and why use it?
Sabre GDS API Configuration links your Sabre account to QuoteCloud so booking data can be imported automatically and formatted into professional travel itineraries. This saves manual work and reduces errors by letting QuoteCloud, a sales quoting software and sales proposal software, generate client-ready itineraries directly from GDS bookings.
How do I connect my Sabre GDS account to a QuoteCloud team?
To connect Sabre to a team: open QuoteCloud Settings from the Dashboard, go to Users & Roles → Teams, select the team and click Edit, then open Travel API Settings. Under the Sabre GDS tab set the connection type to Authenticate via Downline API Order, choose the itinerary template containing an Itinerary Placeholder, enter your Sabre credentials (Queue Number, Domain, PCC, User ID, Password), click Save, and then verify the template.
Which Sabre credentials and settings are required to set up the integration?
You must provide the Sabre connection details: Queue Number, Domain, PCC (Pseudo City Code), User ID and Password. In Travel API Settings set the connection type to Authenticate via Downline API Order. After entering these fields, click the green Save button to store and activate the team’s Sabre configuration.
How do I configure itinerary templates so Sabre bookings populate correctly?
Choose an itinerary template in the team’s Travel API Settings and ensure that template contains an Itinerary Placeholder where Sabre booking data will be injected. After saving the Sabre configuration, open the selected template to confirm placeholders are positioned correctly and that layout, branding, and any additional content blocks render as expected.
Can different teams in QuoteCloud use different Sabre settings or templates?
Yes. QuoteCloud lets each team maintain separate Travel API and itinerary integration settings. Configure Sabre credentials and select the itinerary template per team so different business units can use distinct Sabre connections and templates.
How can I verify the Sabre integration is working after setup?
After saving the Sabre settings, open the itinerary template you selected and confirm the Itinerary Placeholder is present. Then trigger a test import or open a Sabre-generated itinerary in QuoteCloud to confirm booking data populates automatically. If data appears in the placeholder and the document formats correctly, the integration is active.
What should I do if Sabre itineraries fail to import or placeholders don’t populate?
Check the team’s Travel API Settings to ensure the connection type is Authenticate via Downline API Order and all Sabre credentials (Queue Number, Domain, PCC, User ID, Password) are correct. Confirm the selected itinerary template includes an Itinerary Placeholder and that you clicked Save to activate the settings. If issues persist, re-test with a known booking and contact QuoteCloud support or your Sabre administrator for assistance.
Can I enhance Sabre-generated itineraries in QuoteCloud and deliver them to travellers on mobile?
Yes. Once Sabre booking data is imported, QuoteCloud lets you enrich itineraries with destination guides, photos, PDFs, videos, and reusable content blocks to create more compelling proposals. You can also provide travellers with mobile access via the TravelDocs app so customers view trip details and documents on the go. This makes QuoteCloud a flexible quote software and proposal software solution for travel teams.