What does it mean?
Embarking on a seamless integration process is crucial when onboarding new Online Travel Agencies (OTAs) to City Sightseeing through TourCMS. In this guide, we will outline the precise steps to be followed for a successful connection, ensuring a streamlined experience across various currency accounts—GBP, EUR, or USD. Navigating through these steps will pave the way for a smooth and efficient partnership, enhancing the collaborative synergy between City Sightseeing and its valued OTAs.
What should I do?
Connect Agent ID for OTA to the relevant supplier account ID depending on the products the OTA will book. Ensure to assign option 3 - Connection permissions - Trusted Travel Agent.
Tour Code and Supplier Code:
Each TourCMS Tour ID that will be connected via Prio needs to have Tour Code and Supplier Code filled in under Set Up / Operations & Suppliers. This is information that gets transmitted through API during the booking process so that Prio can recognise and match product/supplier information.
External Agent Credentials:
Prio's Support team can advise on the agent credentials of an OTA within Prio's system. Please contact api-support@prioticket.com in case that agent credentials are missing under the field External Agent Credentials for the specific Agent ID. Please note if an Agent will be booking City Sightseeing products via various accounts (GBP, EUR, USD), the credentials need to be added separately on each of the Agent accounts.
For operators working with Prio:
For instance, Evans Evans uses Prio for redemptions. In such cases, the Family and Student rates must be formatted exactly as specified. If anything else is added, Prio will not recognise them.
Family
Student
Additionally, the time-slot format in the request should be as follows: